Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load test #256

Open
ddfridley opened this issue Aug 20, 2020 · 7 comments
Open

Load test #256

ddfridley opened this issue Aug 20, 2020 · 7 comments
Labels
Node Requires a Node Developer

Comments

@ddfridley
Copy link
Contributor

The november elections are comming. We need a way to load test so that we can optimize our performance. Ideally, the test would load the page (1000's of times in a second), and load all of the referenced images. But caution - we are charged for downloading those videos, so lets try to be careful of that. And, those videos are hosted on a content delivery network and we don't need to test that.

One way to do this would be to use loader.io on heroku. But that's only a possibility to consider.

@ddfridley ddfridley added the Node Requires a Node Developer label Aug 20, 2020
@djbowers djbowers self-assigned this Aug 27, 2020
@djbowers
Copy link
Collaborator

Will start work on this after I finish #237, which I hope to have complete by the end of this week.
Aiming to set up a time early next week to discuss first steps on this issue with @ddfridley

@djbowers
Copy link
Collaborator

djbowers commented Sep 3, 2020

Had a discussion today with David and Dana on this. In addition to loader.io, I am going to investigate the loadtest npm package as an option.

Goal for next week is to run a basic load test with one of the above tools on my Heroku Undebate server.

@djbowers
Copy link
Collaborator

Backing down from this ticket due to starting a new job. @ddfridley will be taking over

@djbowers djbowers removed their assignment Sep 23, 2020
@MrNanosh
Copy link
Collaborator

MrNanosh commented Oct 4, 2020

@ddfridley fridley has tested the load using loader.io with an upgraded Heroku account. The updated Heroku didn't ameliorate the increased load 30 connections per second was 1000 times slower than 1 connection per second with load on the server

@MrNanosh
Copy link
Collaborator

MrNanosh commented Oct 4, 2020

A suggestion: use CloudFront as a CDN as a one step solution to configure caching of web pages.

@ddfridley
Copy link
Contributor Author

ddfridley commented Oct 4, 2020 via email

@ddfridley
Copy link
Contributor Author

ddfridley commented Oct 4, 2020

@ddfridley fridley has tested the load using loader.io with an upgraded Heroku account. The updated Heroku didn't ameliorate the increased load 30 connections per second was 1000 times slower than 1 connection per second with load on the server

@MrNanosh I don't see where you get a 1000x difference.

Connections per second | average response time  (using a hobby level app)
 1 |  45mS
10 | 102mS
20 | 134mS
25 | 112mS
26 | 508mS
27 | 925mS
30 | 1351mS

These measurements have a lot of variation in them. I ran 25 again and got 104mSec, but the trend is apparent in theses small samples.

The test was xx connections per second for 30 seconds.
Here is an example test result: https://bit.ly/33ra8cX

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Node Requires a Node Developer
Projects
None yet
Development

No branches or pull requests

3 participants