ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Rosser <nros...@solveda.com>
Subject Re: Low utilization of OFBiz on multi core servers
Date Wed, 13 Aug 2014 18:22:26 GMT
FWIW -- we went through a lot of performance pains implementing some 
high-volume eComm apps. Ended up consulting directly with David Jones 
for pointers / advise / strategy etc.

As a result we put together this doc, may be of some help / interest:


First section is all about the caching aspects of OFBiz, all the good DB 
caching stuff in the framework.

Scroll down to the "memory" section of the doc ... for a discussion 
about JVM settings etc.


On 8/13/2014 12:53 PM, JFradkin@styleline.com wrote:
> I agree that looking at just CPU is not a good guide.
> IO is usually the issue before cpu. If it was bad code the cpu might go 100%
> before the IO.
> But bus, memory etc all play a part.
> Did you switch to Postgres? Not sure if Derby is the best for load testing.
> I know with postgres each time a request is used it will use a new thread
> and can make use of multiple CPU.
> I am not sure if the JVM uses multiple core, but I imagine it has some form
> of using multiple threads.
> Any how I appreciate your sharing you found 20 concurrent users seems to be
> a max.
> Not 100% sure, but I know I had to support 250 at my last job, but I used
> many techniques.
> For one I had three web servers. My Database server was very high end with
> fiber SAN. I used different app servers for different parts of my app. I was
> using liferay as my portal engine, and I even had a separate server or some
> of our larger clients, while smaller clients used a shared instance.
> I guess my point is there are many ways to get an application to handle the
> load.
> -----
> Joel Fradkin
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/Low-utilization-of-OFBiz-on-multi-core-servers-tp4653440p4653445.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.

View raw message