<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
We had the same (bad) experience with OpenCms XML-content that
reaches a certain amount of items (unfortunately not as many as you
might think).<br>
It's basically as if your database would store every row as XML in a
virtual filesystem. This just can't perform very well at all, the
concept doesn't allow this. <br>
And with something complex like a calendar with events, it goes
totally nuts. A sophisticated calendar is tricky even with a regular
database, with XML content it's server kill. ;)<br>
<br>
Unless OpenCms is offering some database connection features (e.g.
through Hibernate) to avoid storing everything in XML in the VFS,
you do better with a real database solution.<br>
<br>
<div class="moz-cite-prefix">Am 27.03.2015 um 15:15 schrieb Alberto
Gallardo:<br>
</div>
<blockquote
cite="mid:CA+zs-Py4GJEYmyudY5sk90hRrt4EN5yV0w+KkP=CMKJJaaoEjA@mail.gmail.com"
type="cite">
<div dir="ltr">Dear list,
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Removing the calendar from some pages bring us a ten-fold
performance improvement.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div><br>
</div>
<div><br clear="all">
<div>
<div class="gmail_signature">Alberto Gallardo<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>