Conversation
Contributor
|
I'm not sure if you were looking for performance improvements with this, but it looks like we'll be getting one. I know this is a big shift in how kinto works (scaling at the container vs scaling at the app) but here are my results anyways:
With main and uwsgi locked to 1 process: 80 seconds, 2 errors produced. This could be a 34% improvement for performance if you look at test run time, or a 47% improvement if you look at how many concurrent users it can handle. |
alexcottner
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Let's try Granian instead of uwsgi.
Functional tests should pass (if they do, then investigate why they don't on mozilla/remote-settings#1162)