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

Explore performance improvements #187

Open
elrayle opened this issue Sep 12, 2019 · 2 comments
Open

Explore performance improvements #187

elrayle opened this issue Sep 12, 2019 · 2 comments
Assignees
@elrayle
Labels
in progress Low Priority low priority - on the back burner and may not be done qa feature requires code change refactor

Comments

@elrayle
Copy link
Member

elrayle commented Sep 12, 2019 •
edited
Loading

Explore background jobs, concurrency, parallelism, and load balancer as options to improve performance from the QA side.

Request to improve performance on AWS: https://culibrary.atlassian.net/browse/DLITSYS-3436
@elrayle elrayle self-assigned this Sep 12, 2019
@elrayle elrayle added the qa feature requires code change label Sep 12, 2019
@elrayle
Copy link
Member Author

elrayle commented May 12, 2020

Related work:

background jobs: PRs #289, #328, #329, #330, #331, #332, #333 + others

Explored parallelism in QA with mixed results. Large complex authorities generally saw improvement. Smaller, less complex authorities actually got worse. Did not put this in production. Branch on local machine not pushed to GitHub.

@elrayle
Copy link
Member Author

elrayle commented May 12, 2020

This is a lower priority until the cache performance improves. At this point, performance issues in the QA side are drawfed by the performance of receiving cache data.

@elrayle elrayle added the Low Priority low priority - on the back burner and may not be done label May 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elrayle elrayle

Labels
in progress Low Priority low priority - on the back burner and may not be done qa feature requires code change refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@elrayle