Performance tuning...

[appel]

Hi

I am in need of performance tuning my Geronimo (Jetty) server to accommodate
for a specific type of load burst.


The behavior I need to tune Geronimo to handle goes something like this:

- Every minute, 3000 unique clients will load up a set of 4 pages.
- This happens every minute for 10 minutes, so all in all there are 30.000
unique clients that will try to connect and request those 4 pages over a
period of 10 minutes.


The pages are very plain, two html pages, two jsp pages that do minimum
stuff.

The bottleneck here is the number of clients.

How can I performance tune Geronimo (Jetty container) to handle this type of
high client load?

(I've already increased the max-threads to 500, but when I do performance
load-test in JMeter I get lots of errors.)

Thanks.
-- 
View this message in context: 
http://www.nabble.com/Performance-tuning...-tp24320965s134p24320965.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Performance tuning...

[viola.lu]

Any log about your errors? And some suggestions: maximize your OS tcp
connections and open file descriptors, on linux:
modify /etc/sysctl.conf with net.ipv4.ip_local_port_range = 1024 65000 ,this
will promise about 6000 tcp connections and run sysctl -p to check whether
this setting works fine.

modify /etc/security/limits.conf with 
root soft nofile 10240 #you can change 10240 as you would like
root hard nofile 10240

edit /etc/pam.d/login with
session required pam_limits.so

Pls try it!


appel wrote:
 
 Hi
 
 I am in need of performance tuning my Geronimo (Jetty) server to
 accommodate for a specific type of load burst.
 
 
 The behavior I need to tune Geronimo to handle goes something like this:
 
 - Every minute, 3000 unique clients will load up a set of 4 pages.
 - This happens every minute for 10 minutes, so all in all there are 30.000
 unique clients that will try to connect and request those 4 pages over a
 period of 10 minutes.
 
 
 The pages are very plain, two html pages, two jsp pages that do minimum
 stuff.
 
 The bottleneck here is the number of clients.
 
 How can I performance tune Geronimo (Jetty container) to handle this type
 of high client load?
 
 (I've already increased the max-threads to 500, but when I do performance
 load-test in JMeter I get lots of errors.)
 
 Thanks.
 

-- 
View this message in context: 
http://www.nabble.com/Performance-tuning...-tp24320965s134p24321181.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Could not resolve reference for persistence/jpaEntity#org.apache.geronimo.persistence.PersistenceUnitGBean

[Shawn Jiang]

I'm not sure because I never used Oracle with Geronimo before.

Can you please create a standalone NonJta instead of reusing the JTA as the
Non-JTA ?

Note: There is no way to create a single module that contains both JTA and
Non-JTA DS with console wizard.  See: [1], You need to use the database pool
wizard again to create another module for Non-JTA. and add this module as a
dependency just like the JTA module.

[1] https://issues.apache.org/jira/browse/GERONIMO-4331

On Fri, Jul 3, 2009 at 6:16 AM, pookie1973 christopher.ad...@nhs.netwrote:


 Shawn,

 I've added a none JTA data source to the persistence.xml, and changed the
 transaction type to resource local, I now get:-

 Unable to resolve reference NonJtaDataSourceWrapper
 in gbean

 default/jpaTest/1.0/car?EJBModule=jpaFacade.jar,J2EEApplication=default/jpaTest/1.0/car,PersistenceUnitModule=jpaEntity.jar,j2eeType=PersistenceUnit,name=jpaEntity
to a gbean matching the pattern
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
due to: No matches for referencePatterns:
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
 Unable to resolve reference JtaDataSourceWrapper
in gbean

 default/jpaTest/1.0/car?EJBModule=jpaFacade.jar,J2EEApplication=default/jpaTest/1.0/car,PersistenceUnitModule=jpaEntity.jar,j2eeType=PersistenceUnit,name=jpaEntity
to a gbean matching the pattern
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
due to: No matches for referencePatterns:
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
 org.apache.geronimo.common.DeploymentException: Unable to resolve reference
 NonJtaDataSourceWrapper
 in gbean

 default/jpaTest/1.0/car?EJBModule=jpaFacade.jar,J2EEApplication=default/jpaTest/1.0/car,PersistenceUnitModule=jpaEntity.jar,j2eeType=PersistenceUnit,name=jpaEntity
to a gbean matching the pattern
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
due to: No matches for referencePatterns:
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
 Unable to resolve reference JtaDataSourceWrapper
in gbean

 default/jpaTest/1.0/car?EJBModule=jpaFacade.jar,J2EEApplication=default/jpaTest/1.0/car,PersistenceUnitModule=jpaEntity.jar,j2eeType=PersistenceUnit,name=jpaEntity
to a gbean matching the pattern
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
due to: No matches for referencePatterns:
 [?name=OracleDS#org.apache.geronimo.naming.ResourceSource]
 at

 org.apache.geronimo.deployment.DeploymentContext.getConfigurationData(DeploymentContext.java:672)
 at
 org.apache.geronimo.deployment.Deployer.install(Deployer.java:332)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:256)
 at
 org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at

 org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at

 org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
at

 org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867)
at
 org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239)
at

 org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116)
at

 org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61)
at java.lang.Thread.run(Unknown Source)

 My understanding of a JTA data source is that it supports distributed
 transactions (XA) and that a none JTA data source only supports local
 transactions. I'm using the Oracle thin driver which supports both JTA and
 none JTA transactions, therefore I have specified the same data source for
 both transaction types.

 Please advise.

 Regards,

 Chris


 http://www.nabble.com/Could-not-resolve-reference-for-persistence-jpaEntity-org.apache.geronimo.persistence.PersistenceUnitGBean-tp24191944s134p24238070.html


 pookie1973 wrote:
 
  I'm using Geronimo 2.1, I have an ear file containing an EJB project with
  a single stateless session bean and a JPA project containing four entity
  beans. When I export the ear file and deploy it to Geronimo via the
  console, I get:-
 
  At least one deployment
  problem:[org.apache.geronimo.common.DeploymentException: Could not
 resolve
  reference at deploy time for query
 
 ?name=persistence/jpaEntity#org.apache.geronimo.persistence.PersistenceUnitGBean.
  No GBean references found.]
  org.apache.geronimo.common.DeploymentException: At least one deployment
  problem:[org.apache.geronimo.common.DeploymentException: Could not
 resolve
  reference at deploy time for query
 
 

Re: Performance tuning...

[Gianny Damour]

Hi,

I believe you should deploy an HTTP cache in front of Geronimo. You  
will observe way better performance improvements using this approach  
than by trying to tune Geronimo. You may want to have a look at Squid:


http://www.squid-cache.org/


If your two JSP pages are client specific, split them into client  
specific and client agnostic fragments and use a caching engine to  
cache the client agnostic fragments.


Thanks,
Gianny

On 03/07/2009, at 8:31 PM, appel wrote:



Hi

I am in need of performance tuning my Geronimo (Jetty) server to  
accommodate

for a specific type of load burst.


The behavior I need to tune Geronimo to handle goes something like  
this:


- Every minute, 3000 unique clients will load up a set of 4 pages.
- This happens every minute for 10 minutes, so all in all there are  
30.000
unique clients that will try to connect and request those 4 pages  
over a

period of 10 minutes.


The pages are very plain, two html pages, two jsp pages that do  
minimum

stuff.

The bottleneck here is the number of clients.

How can I performance tune Geronimo (Jetty container) to handle  
this type of

high client load?

(I've already increased the max-threads to 500, but when I do  
performance

load-test in JMeter I get lots of errors.)

Thanks.
--
View this message in context: http://www.nabble.com/Performance- 
tuning...-tp24320965s134p24320965.html
Sent from the Apache Geronimo - Users mailing list archive at  
Nabble.com.