You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Jacques Le Roux <ja...@les7arts.com> on 2014/09/04 14:22:48 UTC
Re: Low utilization of OFBiz on multi core servers
Le 13/08/2014 20:22, Nick Rosser a écrit :
> 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:
>
> http://bigfish.solveda.com/help/guideCachingAndMemory.htm
>
> 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.
Interesting, thanks Nick.
I noticed there is a known bug
<<TECH NOTE: The EXP and SR misses do not currently work on OFBiz due to a bug introduced a few years ago. All misses are logged as NF (Not Found).>>
Do you have more information about that, is it only on the UI side? Is it only information missing there, or? Is there a Jira issue open, etc?
Jacques
>
> Nick
>
> 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.
>
Re: Low utilization of OFBiz on multi core servers
Posted by Jacques Le Roux <ja...@les7arts.com>.
I believe it's only about the UI, so nothing really important, I did not check code though
I also noticed there is a small error in <<Back-End Database “Update”>> section
The modified ST_ID is 5 (from Yellow to Black Pants) not 6
The (stType = 2) is correct though
HTH
Jacques
Le 04/09/2014 15:17, Nick Rosser a écrit :
> <<TECH NOTE: The EXP and SR misses do not currently work on OFBiz due to a bug introduced a few years ago. All misses are logged as NF (Not Found).>>
>
> I have to think that this was direct feedback from David Jones. Perhaps it is resolved now, not sure to be honest.
>
> On 9/4/2014 8:22 AM, Jacques Le Roux wrote:
>>
>> Le 13/08/2014 20:22, Nick Rosser a écrit :
>>> 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:
>>>
>>> http://bigfish.solveda.com/help/guideCachingAndMemory.htm
>>>
>>> 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.
>>
>> Interesting, thanks Nick.
>>
>> I noticed there is a known bug
>> <<TECH NOTE: The EXP and SR misses do not currently work on OFBiz due to a bug introduced a few years ago. All misses are logged as NF (Not Found).>>
>>
>> Do you have more information about that, is it only on the UI side? Is it only information missing there, or? Is there a Jira issue open, etc?
>>
>> Jacques
>>
>>>
>>> Nick
>>>
>>> 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.
>>>
>
Re: Low utilization of OFBiz on multi core servers
Posted by Nick Rosser <nr...@solveda.com>.
<<TECH NOTE: The EXP and SR misses do not currently work on OFBiz due to
a bug introduced a few years ago. All misses are logged as NF (Not
Found).>>
I have to think that this was direct feedback from David Jones. Perhaps
it is resolved now, not sure to be honest.
On 9/4/2014 8:22 AM, Jacques Le Roux wrote:
>
> Le 13/08/2014 20:22, Nick Rosser a écrit :
>> 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:
>>
>> http://bigfish.solveda.com/help/guideCachingAndMemory.htm
>>
>> 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.
>
> Interesting, thanks Nick.
>
> I noticed there is a known bug
> <<TECH NOTE: The EXP and SR misses do not currently work on OFBiz due
> to a bug introduced a few years ago. All misses are logged as NF (Not
> Found).>>
>
> Do you have more information about that, is it only on the UI side? Is
> it only information missing there, or? Is there a Jira issue open, etc?
>
> Jacques
>
>>
>> Nick
>>
>> 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.
>>