Open
Bug 343346
Opened 19 years ago
Updated 11 years ago
[mod_perl] Cache Bugzilla->template per-process to improve performance
Categories
(Bugzilla :: Bugzilla-General, enhancement, P4)
Tracking
()
NEW
People
(Reporter: mkanat, Unassigned)
References
Details
Right now we're creating a new Bugzilla->template on each request.
Instead, it might be better to just keep re-using the Template object over and over as long as we're in the same process. This would also let us take advantage of the Template-Toolkit cache, where it's already loaded the template code into memory and doesn't even have to read the disk for the data.
Comment 1•16 years ago
|
||
mkanat what is involved with this request?
Reporter | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> mkanat what is involved with this request?
Discovering a working way to cache items per-process under mod_perl.
Reporter | ||
Comment 3•16 years ago
|
||
Oh, and then making sure that Template-Toolkit doesn't leak like crazy across requests.
Reporter | ||
Updated•15 years ago
|
Priority: -- → P4
![]() |
||
Comment 4•13 years ago
|
||
glob: didn't you fix that in bug 778631?
(In reply to Frédéric Buclin from comment #4)
> glob: didn't you fix that in bug 778631?
bug 778631 implements a single Template::Provider object per process, which is different from a Bugzilla::Template object per process. there may be additional gains by caching the main template object, as this is the recommended mod_perl deployment strategy for template-toolkit.
You need to log in
before you can comment on or make changes to this bug.
Description
•