Closed
Bug 894616
Opened 11 years ago
Closed 10 years ago
Turn on jinja byte code cache
Categories
(Marketplace Graveyard :: Code Quality, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: andy+bugzilla, Unassigned)
References
Details
(Keywords: perf)
The jinja byte code caching is turned off:
https://github.com/mozilla/zamboni/commit/e99c019da5d7329f98c83a34645e2fb0636acdf6
But nobody can remember why. It would be good to have this turned on, last time I tried, I don't remember it making a significant difference to performance. That might have changed or I might have been doing it wrong. So let's see if it does and if everything still works.
Comment 1•11 years ago
|
||
We did a quick load test with MemcacheBytecodeCache enabled and the results were not promising. We saw higher CPU usage and slower response times.
Reporter | ||
Updated•11 years ago
|
Priority: -- → P4
Comment 2•11 years ago
|
||
Curious if the CPU usage was a "thundering herd" problem? Can we compile the templates when we deploy?
Comment 3•11 years ago
|
||
Is this something we want anyway since the highest-trafficked templates have been moved to the client? If we keep up with APIing everything, this won't be doing much.
Updated•10 years ago
|
Blocks: marketplace-perf
Reporter | ||
Comment 4•10 years ago
|
||
Agree with comment 3, we want to move to an API and have as few templates on the server as possible.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•