autopush-rs
autopush-rs copied to clipboard
mozilla-services
feat: Load test fixups
Some minor tweaks to the load tests to make them easier to run locally.
These include:
- normalizing the
--configoption across binaries (this is not used in production) - Change the load test to use a hash of the payload instead of the payload itself (freeing memory and making checks faster)
- Make the
WORKER_COUNTan environment parameter
I ran this locally and was getting some errors.
@Trinaa says that this is from a race condition that comes from using dict's as the data type for storing the records. I want to look into this a bit so I can understand what is happening.
I guess I'm not running the load tests correctly, because I'm not seeing those failures:
(This is with both the load tests and servers running on my local machine. There are a bunch of connection refused errors, but those are to be expected.)
boosting the local ulimit to 2048 also helped with some of the file handle problems.
I guess I'm not running the load tests correctly, because I'm not seeing those failures...
@jrconlin the list of request names looks a bit short in your screenshot. There should be some POST notification - send and WSS notification - recv in there...
Yeah, I realized that I was running low on node handles. I ran another test now that I've kicked the count up to stupid levels.
The 1 failure was a database save error resulting in a 503
Yeah, I realized that I was running low on node handles. I ran another test now that I've kicked the count up to stupid levels.
The 1 failure was a database save error resulting in a 503
Can you try running against the stage server? The URL should be set by default.
I can, the reason I was running locally was to load test dual mode. (I had configured autopush to run as that locally as well) I'm presuming that stage is still configured to run against the default dynamodb, which is fine, since we can get a good baseline that way. I'll work with @emaydeck-mozilla about what the dual configuration should be.