[opencms-dev] Lessons learned with the calendar

[Alberto Gallardo]

> 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.
> 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. ;)
>

Well, for OpenCms inexperienced programmers it's even more surprising, as
to avoid xml serialization, the calendar stores the relevant data as
properties. These properties are stored as plain text in the database.

With regard to the performance, several tests suggest that the processing
time in such scenarios is not lineal with respect to the number of
properties read. It seems as if there were some penalties due to memory
resizing operations.



> 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.
>

But don't forget that one of the problems that OpenCms has to solve is the
permissions check.

Regards,

Alberto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20150328/7bb2b3fc/attachment.htm>