-
Notifications
You must be signed in to change notification settings - Fork 70
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 Authenticated GET requests to various content types #9203
Labels
Comments
ElijahLynn
changed the title
We discussed in planning now, that the public API requests will be authenticated so it is still worth testing authenticated GET requests. I finally got Goose Load Testing working with concurrent requests on Friday so we should still pull in a new story this sprint to get these metrics on the authN GET requests.
Load test Authenticated GET requests to various content types
May 23, 2022
Working on getting requests routed through our SOCKS proxy with Goose > tag1consulting/goose#490 |
25 tasks
cd tests/loadtest
# Start SOCKS PROXY FIRST
export ADMIN_USERNAME="content_build_api"
export ADMIN_PASSWORD="drupal8"
cargo run --release -- --host https://staging.cms.va.gov --report-file report-file.html --running-metrics 1 --users 125 --hatch-rate 10 --run-time 3m --no-reset-metrics
|
I cannot upload HTML files but here is the HTML report zipped up from this command, and I took a full page screenshot too: cargo run --release -- --host https://staging.cms.va.gov --report-file report-file.html --running-metrics 1 --users 125 --hatch-rate 10 --run-time 3m --no-reset-metrics |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #8080 we got some baseline metrics for anonymous GET requests to the Benefits Detail Page which was around 217/second. We now need to test authenticated GET requests to various content types as that will be reflective of real world traffic when the new Next.js build system evolves to allowing for public requests.
AC
Tasks
Originally posted by @ElijahLynn in #8050 (comment)
The text was updated successfully, but these errors were encountered: