[opencms-dev] Lessons learned with the calendar

[Alberto Gallardo]

Dear list,

in the last OpenCms days I talked to some of you mentioning some
performance problems we were facing. I got some valuable input and was
asked to share our findings, in case we further analyzed the situation.

Today, seizing Deiversons Silveira post 'Problem with lucene - Old
Generation Memory', I wanted to share with you the main conclusion after
our analysis: we found that the alkacon-oamp/calendar was responsible for
most of the server processing time.

It turns out that this component aggregates all existing events under a
configured folder. It doesn't make any difference if these are old or not.
Even with the OCEE accelerator, building the calendar view is a very
expensive operation.

Removing the calendar from some pages bring us a ten-fold performance
improvement.

Just keep in mind that content aggregation in OpenCms isn't for free. It
takes a lot of memory and processing time. I'm talking about querying 5
properties of some 3000 events. So many elements it's probably not that
common, but if you are not aware of it, and you have been using similar
components (e.g. lists) accumulating ballast during several years, it could
inadvertently affect you some day.

Regards,



Alberto Gallardo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20150327/786e5ea3/attachment.htm>