This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
I have developed an application using Liferay 5.2.3 and its working fine.While doing performance testing, the application takes nearly 365% of cpu usage.Even though we have tested plain liferay bundle it took more than 290% of cpu usage. The code base is not that much heavy(there is no high business logic ) and we are following liferay's performance tuning steps like fast loading of images,css,disabled unused filters in liferay and using hibernate calls to hit database.The application is running in the system which is configured with the configuration mention in liferay specification. Eventhough we have followed the steps we couldn't reduce the cpu usage percentage.
Please suggest us to resolve this .
Thanks in advance.
All search starts with beginner's luck and all search ends with victor's severly tested.
As an infrastructure portal, the portal can support over 3300 concurrent users on a single server with mean login times under 0.5 a second and maximum throughput of 79+ logins per second. In collaboration and social networking scenarios, each physical server supports over 1300 concurrent users at an average transaction times of under 800 ms. Note that this benchmark was generated based on the application server: 2 x Intel Core 2 Quad E5430 2.66GHz CPU, 12MB L2 cache (8 cores total), 8GB memory, 2 x 146GB 10k RPM SCSI, CentOS 5.2 64-bit Linux.
The portal's CMS/WCM scales to beyond 150,000 concurrent users on a single Portal server with average transaction times under 50ms and 35% CPU utilization. Given sufficient database resources and efficient load balancing, the portal can scale linearly as one adds additional servers to a cluster. How do we achieve this? Here we list TEN golden rules:
• Adjust the server's thread pool and JDBC connection pool:. By default, the portal is configured for a maximum of 100 database connections. For Tomcat and JBoss, a good number is between 200 and 400 threads in the thread pool.
• Turn off unused servlet filters: Servlet filters dynamically intercept requests and transform them. The portal contains more than 20 servlet filters, so turn off the ones you aren't using.