Hello
There is a big startup cost to beaker caching at my experience (file
and memory backend), and since the code shows it is made to ensure
data are not corrupted amongst all instances the more instances you
have the more time it needs to ensure transactions. (stuff about
lock...). Therefore the cost should increase with the number of
instances.
Profile your application, try to decorate beaker cache to see how much
time it takes. My intuition could prove wrong one should always make
optimisation on behalf of measures not of intuition :)
Hf, gl
Le 9 oct. 2011 à 20:00, Rotem Tamir <[email protected]> a écrit :
Carlos hi and thanks for the quick response,
I am using a lot of beaker memory caching for almost all of my DB
queries, and the controller function i'm load testing has no
repoze.who decorator...
It's responding real real slow...
On Oct 9, 7:52 pm, Carlos Daniel Ruvalcaba Valenzuela
<[email protected]> wrote:
Perhaps you should do a few more tests, try to know where the
bottleneck
really is, is it the temples? Caching? Or some other thing? I
remember a
post a fewdays ago about how report.who and report.what would add 3
db
queries for auth. Check the mailing list archives there has been some
discussion on this already that could be useful.
--
You received this message because you are subscribed to the Google
Groups "TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
