Liferay

Hello

I have been doing performance testing of Liferay 5.1.0 running on a machine running on Intel Quad Core 2.67GHz CPU and Linux for the last couple of weeks.

I have written an article about my findings, you can read my article here. The article contains links to the JMeter test scripts used, and also detailed test results, analysis and areas for further investigation.

I am happy with the performance numbers when I test one URL, the "/web/guest/home". My tests then show that Liferay 5.1.0 can deliver 2200 requests per second, with average response time well under 1 second, when between 1000 and 5000 users are simultaneously hitting the server.

However, when I use the test which samples the 7500 different URLs for the sample Liferay website that was shipped as part of Liferay 5.0.0, I observe a significant performance drop. Liferay is then only able to serve 26 requests per second. I believe this is caused by the fact that memory set aside for caching pages, I guess the EhCache configuration, is so small, that each page has to be generated by the JSP engine.

Comments on my performance testing are appreciated. If anyone as some useful tips on how to easily improve or check the reasons for the major drop in performance to only 26 requests per second, I will look into them, and rerun some of the tests.

Regards
Alf Hogemark

Hi

Thanks for the reply.

I was using Liferay 5.1.0 codebase, and the sample Liferay database from version 5.0.0, where the database was running on MySQL.

I executed your query, and you are correct, the cacheable property was 0 for all rows.

I will set all these to 1, and then rerun some of the tests, and repost my results, but I have a feeling that your suggestion will improve the performance greatly.

Thanks again
Alf

This is very interesting. Performance is still my only concern about Liferay. We are planning to do some performance tests too. We're running Liferay now on a dual Opteron server with 16 GB ram. This server runs two tomcat servers for Liferay (5.0.1, we're planning to upgrade to 5.1.x but we're having some problems with the ajax stuff in wicket) (test and production) and a third tomcat for a Solr index which we use in our portlets (Wicket based).

Pages are served according to YSlow between 1 and 4 seconds (which is too slow at the moment). I'll run some JMeter tests and hope to get started with Yourkit or some other profiler.