You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
I was running a long running stress test for beta release. I configured the test to load 100K random integers and then sleep for 3min. The sleep time was too long and it was not keeping the cluster busy. Below is a graphite plot of notifications queued over time.
Need to do something besides just sleep. Could possibly wait for the # of notifications to drop below a certain amount before running the next load job. This could be a function of the amount we are loading. For example when loading 100K, could wait until the # of notifications drops below 5x100K before starting the next load job.
The text was updated successfully, but these errors were encountered:
I was running a long running stress test for beta release. I configured the test to load 100K random integers and then sleep for 3min. The sleep time was too long and it was not keeping the cluster busy. Below is a graphite plot of notifications queued over time.
Need to do something besides just sleep. Could possibly wait for the # of notifications to drop below a certain amount before running the next load job. This could be a function of the amount we are loading. For example when loading 100K, could wait until the # of notifications drops below 5x100K before starting the next load job.
The text was updated successfully, but these errors were encountered: