927792 - loadtest the read-only addons registration API.

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: API, defect)

Description

[Alexis Metaireau (:alexis)]

We need to know how many RPS we are able to do with the addons registration project.
The testing will be done using different backends and the goals are to:

- Identify the bottlenecks (database? WSGI layer? caching?)
- Identify which backends are the more efficient.
- Determine how many requests per second we can do with a single machine.

Comment 1

[Alexis Metaireau (:alexis)]

Just added a loadtesting script (see https://github.com/mozilla/addon-registration/commit/8033a91f38652ee61df5e0a003cba18c15c8876e).

Next step is to deploy a box on AWS and add a few rows there.

Comment 2

[James Bonacci [:jbonacci]]

Also, I can check this out just to see how the code works - either on my Mac, a VM, or a small AWS instance...

It sounds like you are creating a dummy DB on the fly for the purposes of load testing?

Comment 3

[Alexis Metaireau (:alexis)]

That's it, I need to setup the service in a particular state to be able to load test it.

Comment 4

[Alexis Metaireau (:alexis)]

I'll describe here all the things that are interesting to test. The goal is to test the different backends to know which ones are better fitted for addons reg.

I'm also keen on doing some experimentation on changing the linux kernel scheduler to see if that changes the performances there.

Comment 5

[Wil Clouser [:clouserw]]

Thanks for filing this.  Due to resource constraints we are closing bugs which we won't realistically be able to fix.  If you have a patch that applies to this bug please reopen.

For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/