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.

Sign up for GitHub

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

Jump to bottom

Performance testing and fine tune: Slow API response with CMS timeout settings #3729

Closed
6 tasks
Tracked by #137
patphongs opened this issue Apr 30, 2020 · 1 comment
Closed
6 tasks
Tracked by #137

Performance testing and fine tune: Slow API response with CMS timeout settings #3729

patphongs opened this issue Apr 30, 2020 · 1 comment
Assignees
@lbeaufort
Labels
Needs refinement
Milestone
Sprint 12.3

Comments

@patphongs
Copy link
Member

patphongs commented Apr 30, 2020 •
edited by lbeaufort
Loading

What we're after: In order to ensure the best timeout settings in the CMS, we need to perform load testing in the API and check how long it takes for the CMS to respond.

This work can happen simultaneously with:

Completion criteria:

  • Determine an optimal timeout for CMS api_caller
  • See what the retry settings are - do we need to adjust?

Technical steps

  • Check slowest query times in pg badger over a period of a few months. Try running those queries with Locust
  • Locust test the stage API. Ensure that connections are dropping after the specified interval of time.
  • Determine if the interval of time is too long, if it is, make it a shorter timeout
@patphongs patphongs added this to the Sprint 12.3 milestone Apr 30, 2020
@patphongs patphongs mentioned this issue Apr 30, 2020
Merged
@patphongs patphongs changed the title Performance testing: Slow API response with CMS timeout settings Performance testing and fine tune: Slow API response with CMS timeout settings Apr 30, 2020
@JonellaCulmer JonellaCulmer modified the milestones: Sprint 12.3, Sprint 12.4 May 5, 2020
@lbeaufort lbeaufort modified the milestones: Sprint 12.4, Sprint 12.3 May 5, 2020
@lbeaufort lbeaufort self-assigned this May 5, 2020
@lbeaufort lbeaufort mentioned this issue May 5, 2020
Closed
10 tasks
@lbeaufort
Copy link
Member

Issue moved to fecgov/openFEC #4335 via ZenHub

@patphongs patphongs mentioned this issue Feb 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lbeaufort lbeaufort

Labels
Needs refinement
Projects
None yet
Milestone
Sprint 12.3
Development

No branches or pull requests
3 participants
@patphongs @lbeaufort @JonellaCulmer