i'm trying to implement the module cache. i use the php code mith provided in the theme file:



before the module cache implementation, i have:
Loaded in 0.33 seconds | 36 queries

after i set the module cache, i got:
Loaded in 3.029 seconds | 31 queries

why the loaded time is increasing instead? is it something wrong with loaded time code? as the no of queries is decreasing. the no of query which really matter in this case, am i correct?

one further question, regarding the module cache feature: will it be always work? or is it depending on the programmer whether he implement it or not and it depends on how 'good' he code it (as sometime it won't work if we don't code it good enough)?

thanks in advance!

bump.

Quote:
It sure sounds weird. Is it consistently at 3 seconds instead of .3?

Quote:
It usually works, but is dependant on the module programmer. As described in this thread: Module-wide caching - Important development, a module developer can render the caching feature useless in his or her module. However, since the query count decreases, it seems to work - unless the query count decrease is due to blocks being cached.

yes, it is consistently on the 3 seconds. performance wise i don't see it decreasing. i'm not sure either...

i think i ever saw this kind of issue reported by other users somewhere. have searched it but couldn't find it.

MySQL debug should help you pin down what is lagging. May want to enable that then check your page.