Closed
Bug 1014157
Opened 11 years ago
Closed 11 years ago
Snippet Service python performance plummets with large snippet images
Categories
(Snippets :: Service, defect)
Snippets
Service
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: osmose, Assigned: osmose)
References
Details
Whenever we create a snippet with an image with a large filesize, the service's performance plummets. On one hand, we should avoid large snippets if possible, but it would also be nice to have an idea of why the service gets so angry when dealing with snippets over 150kb and how we can fix that.
Here's a link to New Relic during the time of our last incident: https://rpm.newrelic.com/accounts/263620/applications/2904874?tw[end]=1397499960&tw[start]=1396895160
Here's the transaction view for the main snippets view at that time: https://rpm.newrelic.com/accounts/263620/applications/2904874/transactions?tw[end]=1397499960&tw[start]=1396895160&type=app#id=309252923
Almost all the time is spent in WSGI/Response, which according to http://stackoverflow.com/questions/20214508/analyzing-high-wsgi-response-time-data-of-django-with-mod-wsgi-on-newrelic is the time it takes for WSGI to pull strings out of our response and send them to the client.
Could this be roughly as fast as we could send that data out? Could we be any faster? Is there a reason why, even with the load balancer, the Python app is still getting hammered like this?
Updated•11 years ago
|
Assignee: nobody → mkelly
Comment 1•11 years ago
|
||
We'll be working with jakem on the infrastructure side of this project.
Updated•11 years ago
|
Assignee | ||
Comment 2•11 years ago
|
||
We just finished testing the effects of bug 1091939 and were able to send out 4 megabytes of snippets data to release with no issues, so I think we can call this resolved.
You need to log in
before you can comment on or make changes to this bug.
Description
•