You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by jpekki <ja...@ec.europa.eu> on 2006/10/27 17:04:29 UTC
Cache invalidated after a comment was added -> Poor performance
We have done performance analysis of Roller 2.3 on our configuration. We
noticed that when you create a comment, cache gets invalidated and
rebuilding the cache will take substantial amount of time, even in case of
top notch hardware. This may lead up to 40 seconds delay for the next one to
access the pages.
Our comments are moderated once or twice a day, so invalidating cache is not
necessary in our case. Is there any way to change the configuration of
Roller 2.3 so that cache will not be recreated each and every time someone
adds a new comment?
Many thanks in advance for an answer.
Best regards,
Jari
--
View this message in context: http://www.nabble.com/Cache-invalidated-after-a-comment-was-added--%3E-Poor-performance-tf2521138s12275.html#a7032062
Sent from the Roller - Dev mailing list archive at Nabble.com.
Re: Cache invalidated after a comment was added -> Poor performance
Posted by jpekki <ja...@ec.europa.eu>.
Thank you very much for your quick answer, Allen!
Do you think this could be changed in a future version of Roller as an
"out-of-the-box" feature?
Jari
Allen Gilliland-3 wrote:
>
> That's a good point. Unfortunately there is no configurable way to do
> that, it's just something that is built into the code. So your only
> option would be to grab the code from svn and modify that part.
>
> -- Allen
>
>
> jpekki wrote:
>> We have done performance analysis of Roller 2.3 on our configuration. We
>> noticed that when you create a comment, cache gets invalidated and
>> rebuilding the cache will take substantial amount of time, even in case
>> of
>> top notch hardware. This may lead up to 40 seconds delay for the next one
>> to
>> access the pages.
>>
>> Our comments are moderated once or twice a day, so invalidating cache is
>> not
>> necessary in our case. Is there any way to change the configuration of
>> Roller 2.3 so that cache will not be recreated each and every time
>> someone
>> adds a new comment?
>>
>> Many thanks in advance for an answer.
>>
>> Best regards,
>> Jari
>
>
--
View this message in context: http://www.nabble.com/Cache-invalidated-after-a-comment-was-added--%3E-Poor-performance-tf2521138s12275.html#a7033375
Sent from the Roller - Dev mailing list archive at Nabble.com.
Re: Cache invalidated after a comment was added -> Poor performance
Posted by Allen Gilliland <al...@sun.com>.
That's a good point. Unfortunately there is no configurable way to do
that, it's just something that is built into the code. So your only
option would be to grab the code from svn and modify that part.
-- Allen
jpekki wrote:
> We have done performance analysis of Roller 2.3 on our configuration. We
> noticed that when you create a comment, cache gets invalidated and
> rebuilding the cache will take substantial amount of time, even in case of
> top notch hardware. This may lead up to 40 seconds delay for the next one to
> access the pages.
>
> Our comments are moderated once or twice a day, so invalidating cache is not
> necessary in our case. Is there any way to change the configuration of
> Roller 2.3 so that cache will not be recreated each and every time someone
> adds a new comment?
>
> Many thanks in advance for an answer.
>
> Best regards,
> Jari