Hi Mattias, We're on 4.4.x, and performance is generally very good. Not sure we have the same load as you though.
I'm wondering why the requests aren't being answered from the cache? If magnolia can serve the requests from its cache, I think performance will probably be much improved - magnolia won't have to access JCR or render the content. To get magnolia to cache the page you need to make sure the requests are not using parameters (although this depends on your cache settings, of course). Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Mattias Olofsson (via Magnolia Forums) Gesendet: Freitag, 17. August 2012 10:45 An: Magnolia User List Betreff: [magnolia-user] Help with performance problem in Magnolia 4.4.2 Hi, I work as a Consultant in sweden for a big Magnolia customer stationary in Stockholm. We have experience som performance issues with our installation of Magnolia 4.4.2 (bundled with Jackrabbit 1.6.2) under certain load factors. Under normal load on the website we have no problem with our load balanced magnolia instances, but when we get some extra load (we temporary attract more customers to the site by sending out newsletter) we experience some major performance issues. The page that we send the customers to is only a "normal" page with no extra logic/integrations on so Magnolia should be able to handle the request very fast. When we have approx. 200 concurrent requests to the page we get a mean response time on 8-10 seconds For 500 concurrent requests we have a mean response time on 18-20 seconds When we pinpoint the location of the bottleneck (by making stack dump and see what all the threads are waiting on) we see that there is are a lot of synchronization going on in order to retrieve the content node/properties in the magnolia codebase and also in the Jackrabbit codebase. Questions: * Are there someone else that has experience some similar performance issues and can recommend a solution and/or where we can read more about this? * Are there some settings in Magnolia or Jackrabbit that can speed this thing up or which of the synchronization, we do not care in these case if there are any dirty read on the content node/properties? * Is this a known problem in Magnolia 4.4.2 or in general with the Magnolia 4.x.x codebase ? * Is this a known problem in Jackrabbit 1.6.2 or the Jackrabbit 1.x.x codebase? * We read about the Jackrabbit issues noted here, http://documentation.magnolia-cms.com/releases/4-4-9.html, and have tried to upgrade to Magnolia 4.4.9-jr24 (Jackrabbit 2.4.2) but we experience the same performance problem or even WORSE performance. Is this a known problem in Magnolia 4.4.9-jr24 (Jackrabbit 2.4.2)? Our installation: * 2 x Magnolia 4.4.2 (bundled with Jackrabbit 1.6.2) * Loadbalancer in front with sticky on ip (-> session) * db2 database backend for content store -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=e27e2c42-55d0-4364-814b-d9017a46e11b ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
