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 graphs not available on AWS #193

Open
elrayle opened this issue Sep 13, 2019 · 1 comment
Open

Performance graphs not available on AWS #193

elrayle opened this issue Sep 13, 2019 · 1 comment
Assignees
@elrayle
Labels
in progress Moderate Priority moderate priority - probably needed but not critical at this time qa feature requires code change refactor Systems Infrastructure work primarily by sysopts

Comments

@elrayle
Copy link
Member

elrayle commented Sep 13, 2019

The AWS elastic beanstalk instance for culit/qa_server is not able to display graphs using ImageMagick. Unknown cause.
@elrayle elrayle self-assigned this Sep 13, 2019
@elrayle elrayle added the Systems Infrastructure work primarily by sysopts label Sep 13, 2019
@elrayle
Copy link
Member Author

elrayle commented May 12, 2020 •
edited
Loading

This is partially fixed. I can view graphs on AWS integration server, but the performance of generating the graphs make them unusable in production.

The fix for viewing on AWS servers was to move the location of the generated graphs FROM app/assets/images/qa_server/charts TO public/qa_server/charts. This happened in PR #318. See app/services/concerns/qa_server/gruff_graph.rb

To address performance issues in generating graphs, the generation process was moved to background jobs in PRs #329, #330, #331, #332.

There remain issues on the AWS servers for setting up the running of background jobs in background. Sidekiq and Redis are not yet playing nicely with each other which is causing the jobs to still run inline.

@elrayle elrayle added in progress Moderate Priority moderate priority - probably needed but not critical at this time qa feature requires code change refactor labels 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 Moderate Priority moderate priority - probably needed but not critical at this time qa feature requires code change refactor Systems Infrastructure work primarily by sysopts
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@elrayle