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

Research: Enhance CMS performance by freeing up urllib connection pool #3872

Open
3 tasks
Tracked by #137
patphongs opened this issue Jun 29, 2020 · 0 comments
Open
3 tasks
Tracked by #137

Comments

@patphongs
Copy link
Member

patphongs commented Jun 29, 2020

Summary

We may be able to enhance CMS performance by freeing up Django DB connections.

Things to try when locust testing

  • Use non_atomic_requests inside the data views to decrease db transactions. Check to see if the number of CMS DB transactions have decreased. Locust test specifically view functions that utilize non_atomic_requests.
  • See if we need to increase gunicorn workers if non_atomic_requests are freeing up transactions from api_caller dependent view requests.

Related issues

Completion criteria

  • Django DB transactions decrease by using non_atomic_requests
@patphongs patphongs changed the title Research: Enhance CMS performance by modifying connection pooling Research: Enhance CMS performance by freeing up urllib connection pool Jun 29, 2020
@patphongs patphongs self-assigned this Jun 29, 2020
@patphongs patphongs modified the milestones: Sprint 13.2, Sprint 13.3 Jul 30, 2020
@patphongs patphongs removed their assignment Jul 30, 2020
@rfultz rfultz modified the milestones: Sprint 13.9, Sprint 13.10, PI 13 innovation 2 and PI 14 planning Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

4 participants