You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@click.apache.org by "Hans C. Poo" <ha...@welinux.cl> on 2011/09/14 15:49:04 UTC
Recomended performance parameters
Hi,
I'm running a click 2.2 application in a dedicated machine with 32GB RAM and 4 dual core processors, running in Tomcat 6.
I would like to hear some concrete advices to exploit at maximum the machine, with respect to:
- Cayenne object cache (default 10000)
- JVM parameters, Xmx, Xms, Xmn, etc.
- Cayenne cache management
- Other parameters
We have a separate database server machine with postgreSQL, already tunned with pgtune.
The mode in click.xml is in production of course.
I know that this can generate a lot of debate, but i just like to know what may be feasible for this installation.
Thanks
Hans
Re: Recomended performance parameters
Posted by "Hans C. Poo" <ha...@welinux.cl>.
Malcomo,
Thanks for your advice, i'll start pushing load with jmeter and monitor machine at OS level (vmstat 3 running during load) and monitor VM with visualvm or start VM with gc monitoring.
Bye
Hans
Hans Poo, Welinux S.A.
Bombero Ossa #1010, oficina 800,
+56-2-3729770, Movil: +56-9-3199305
Santiago, Chile
----- Mensaje original -----
De: "Malcolm Edgar" <ma...@gmail.com>
Para: user@click.apache.org
Enviados: Jueves, 15 de Septiembre 2011 10:18:15
Asunto: Re: Recomended performance parameters
I would like to swap OGNL with MVEL, but it may cause some backward
compatibility issues.
However in Click OGNL is only use setting property values, in
operations such as form posts. Its not used in read operations, such
as table rendering.
regards Malcolm Edgar
On Thu, Sep 15, 2011 at 10:22 PM, Gilberto <gi...@gmail.com> wrote:
> Malcolm, hope you are well!
> Question inline ...
>
> On Wed, Sep 14, 2011 at 8:26 PM, Malcolm Edgar <ma...@gmail.com> wrote:
>> Hi Hans,
>>
>> The best way to isolate performance issues is to run load tests on a
>> JVM which you are profiling. It is always surprising where the
>> performance issues lie.
>>
>> I would recommend setting up a load tool (JMeter or something similar)
>> which has scripts to hit a number of representative pages. Then run
>> the application in a profiler, or attach a profiler to the JVM and get
>> some metrics on where the application is spending most of its time.
>>
>> With regard to Cayenne, using caching is very important to
>> significantly improve performance. However caching is a tricky
>> subject, especially if you are running multiple web applications on a
>> JVM sharing the same database or across a cluster. This is an area
>> where the Cayenne documentation is quite poor, so you may need to get
>> onto the mail list to get some decent advice.
>>
>
>
>> Also don't use OGNL in your code if you can avoid it. Its performance
>> is quite poor under load, even when using it intelligently. If you
>> need to do expression stuff please use MVEL.
>
> I'm curious about you advice, since Apache Click uses it(OGNL) intensely.
> Can you share a little more about why Apache Click is not using MVEL?
> Is it possible to switch one by the other?
>
> Regards,
>
> Gilberto
>
Re: Recomended performance parameters
Posted by Malcolm Edgar <ma...@gmail.com>.
I would like to swap OGNL with MVEL, but it may cause some backward
compatibility issues.
However in Click OGNL is only use setting property values, in
operations such as form posts. Its not used in read operations, such
as table rendering.
regards Malcolm Edgar
On Thu, Sep 15, 2011 at 10:22 PM, Gilberto <gi...@gmail.com> wrote:
> Malcolm, hope you are well!
> Question inline ...
>
> On Wed, Sep 14, 2011 at 8:26 PM, Malcolm Edgar <ma...@gmail.com> wrote:
>> Hi Hans,
>>
>> The best way to isolate performance issues is to run load tests on a
>> JVM which you are profiling. It is always surprising where the
>> performance issues lie.
>>
>> I would recommend setting up a load tool (JMeter or something similar)
>> which has scripts to hit a number of representative pages. Then run
>> the application in a profiler, or attach a profiler to the JVM and get
>> some metrics on where the application is spending most of its time.
>>
>> With regard to Cayenne, using caching is very important to
>> significantly improve performance. However caching is a tricky
>> subject, especially if you are running multiple web applications on a
>> JVM sharing the same database or across a cluster. This is an area
>> where the Cayenne documentation is quite poor, so you may need to get
>> onto the mail list to get some decent advice.
>>
>
>
>> Also don't use OGNL in your code if you can avoid it. Its performance
>> is quite poor under load, even when using it intelligently. If you
>> need to do expression stuff please use MVEL.
>
> I'm curious about you advice, since Apache Click uses it(OGNL) intensely.
> Can you share a little more about why Apache Click is not using MVEL?
> Is it possible to switch one by the other?
>
> Regards,
>
> Gilberto
>
Re: Recomended performance parameters
Posted by Gilberto <gi...@gmail.com>.
Malcolm, hope you are well!
Question inline ...
On Wed, Sep 14, 2011 at 8:26 PM, Malcolm Edgar <ma...@gmail.com> wrote:
> Hi Hans,
>
> The best way to isolate performance issues is to run load tests on a
> JVM which you are profiling. It is always surprising where the
> performance issues lie.
>
> I would recommend setting up a load tool (JMeter or something similar)
> which has scripts to hit a number of representative pages. Then run
> the application in a profiler, or attach a profiler to the JVM and get
> some metrics on where the application is spending most of its time.
>
> With regard to Cayenne, using caching is very important to
> significantly improve performance. However caching is a tricky
> subject, especially if you are running multiple web applications on a
> JVM sharing the same database or across a cluster. This is an area
> where the Cayenne documentation is quite poor, so you may need to get
> onto the mail list to get some decent advice.
>
> Also don't use OGNL in your code if you can avoid it. Its performance
> is quite poor under load, even when using it intelligently. If you
> need to do expression stuff please use MVEL.
I'm curious about you advice, since Apache Click uses it(OGNL) intensely.
Can you share a little more about why Apache Click is not using MVEL?
Is it possible to switch one by the other?
Regards,
Gilberto
Re: Recomended performance parameters
Posted by Malcolm Edgar <ma...@gmail.com>.
Hi Hans,
The best way to isolate performance issues is to run load tests on a
JVM which you are profiling. It is always surprising where the
performance issues lie.
I would recommend setting up a load tool (JMeter or something similar)
which has scripts to hit a number of representative pages. Then run
the application in a profiler, or attach a profiler to the JVM and get
some metrics on where the application is spending most of its time.
With regard to Cayenne, using caching is very important to
significantly improve performance. However caching is a tricky
subject, especially if you are running multiple web applications on a
JVM sharing the same database or across a cluster. This is an area
where the Cayenne documentation is quite poor, so you may need to get
onto the mail list to get some decent advice.
Also don't use OGNL in your code if you can avoid it. Its performance
is quite poor under load, even when using it intelligently. If you
need to do expression stuff please use MVEL.
regards Malcolm Edgar
On Wed, Sep 14, 2011 at 11:49 PM, Hans C. Poo <ha...@welinux.cl> wrote:
> Hi,
>
> I'm running a click 2.2 application in a dedicated machine with 32GB RAM and 4 dual core processors, running in Tomcat 6.
> I would like to hear some concrete advices to exploit at maximum the machine, with respect to:
>
> - Cayenne object cache (default 10000)
> - JVM parameters, Xmx, Xms, Xmn, etc.
> - Cayenne cache management
> - Other parameters
>
> We have a separate database server machine with postgreSQL, already tunned with pgtune.
>
> The mode in click.xml is in production of course.
>
> I know that this can generate a lot of debate, but i just like to know what may be feasible for this installation.
>
> Thanks
> Hans
>