At 16:48 22/05/2005, you wrote:
Does anyone have any info on Jahia performance..
I am speccing a site for a tender and the current site that will be
replaced is averaging 2,000 visitors an hour, with peaks of 10,000 an hour!
Has Jahia ever been put under this amount of load on any configuration?
Performance is a complex story...
The Jahia load is of course not the same according to several criterias.
- The size of your HTML and back-end caches. 32 bits JVM are limited to 1.5
GB RAM. So, Jahia currently stores in memory the HTML copy of the generated
pages for performance reasons (HTML front-end cache proxy). But this has a
cost in term of memory as we need to store one copy of HTML per mode, per
user, per language, etc...
- The type of page: if you use webapps or complex filters, the performance
is of course not the same than using a standard simple CMS page
- The level of personnalization: as mentionned, there are caches per users.
So if each user has a disctinct login (e.g. SSO), you can not rely on a
similar cache entry for all your users (ex: the same HTML cache entry
available for anonymous).
- The number of authors: naviganting in live mode has not the same cost in
term of CPU/DB than in edit mode. The edit mode needs to check a lot of
more things (locks, display buttons,etc...)
- The clustering scenarios: is there a distinct authoring server (for
example synchronize with the live server evry day), is there a cluster of
Jahia servers, is the search engine working on a distinct machine (PDF
takes a lot of CPU+ time to index for example).
So as you may see, this really depends of your site's configuration and
your site's needs.
Cheers,
St�phane
thanks
Edd
