Hi,
While using JMeter to load test our application, which is deployed separately from the Orbeon War in the same Tomcat, we have noticed that when about 25 JMeter threads are requesting an XForm to be rendered, it takes a number of seconds (around 30 or 40) for the request to be handled. We have also found that over time, Orbeon stops handling these requests and they time out. We have tried increasing the maximum heap size for Java to about 1 Gb and reduced the "maxThreads" in Tomcat to about 10. Has anyone experienced this before? If so, do you have any suggestions on where we can look or what we can change to fix the problem? The specs of our platform are: OS: OpenSuse 11.0 kernal 2.6.25 i686 Java: jdk1.6.0_16 i386 Tomcat 6.0 (executed as a server in Eclipse Galileo) Thanks in advanced, Leon -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Sorry, I should mention that we are using Orbeon 3.7.1
Thanks, Leon On Tue, 2010-01-12 at 17:20 +1100, lmika wrote: > Hi, > > While using JMeter to load test our application, which is deployed > separately from the Orbeon War in the same Tomcat, we have noticed that > when about 25 JMeter threads are requesting an XForm to be rendered, it > takes a number of seconds (around 30 or 40) for the request to be > handled. We have also found that over time, Orbeon stops handling these > requests and they time out. > > We have tried increasing the maximum heap size for Java to about 1 Gb > and reduced the "maxThreads" in Tomcat to about 10. > > Has anyone experienced this before? If so, do you have any suggestions > on where we can look or what we can change to fix the problem? > > The specs of our platform are: > > OS: OpenSuse 11.0 kernal 2.6.25 i686 > Java: jdk1.6.0_16 i386 > Tomcat 6.0 (executed as a server in Eclipse Galileo) > > Thanks in advanced, > > Leon > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
Leon,
These problems are hard to debug through the mailing list. In short: this should not happen, and performance should not degrade in the way you describe. But yes, we have already seen things like this, and they are in general due either to an issue in your application, to a bug or something sub-optimal in Orbeon Forms (which we fix when we find it!), or a configuration issue. When it comes to configuration, see: http://wiki.orbeon.com/forms/doc/developer-guide/performance-tuning#TOC-Reduce-the-number-of-concurrent-pro Unfortunately, you can't configure Tomcat with maxThreads="3", but you can do it with a front-end server. Just for the sake of testing this, could you limit the number of concurrent thread in JMeter to 3? How do things work out when you do that? Alex On Jan 11, 2010, at 10:23 PM, lmika <[hidden email]> wrote: > Sorry, I should mention that we are using Orbeon 3.7.1 > > Thanks, > > Leon > > > On Tue, 2010-01-12 at 17:20 +1100, lmika wrote: >> Hi, >> >> While using JMeter to load test our application, which is deployed >> separately from the Orbeon War in the same Tomcat, we have noticed >> that >> when about 25 JMeter threads are requesting an XForm to be >> rendered, it >> takes a number of seconds (around 30 or 40) for the request to be >> handled. We have also found that over time, Orbeon stops handling >> these >> requests and they time out. >> >> We have tried increasing the maximum heap size for Java to about 1 Gb >> and reduced the "maxThreads" in Tomcat to about 10. >> >> Has anyone experienced this before? If so, do you have any >> suggestions >> on where we can look or what we can change to fix the problem? >> >> The specs of our platform are: >> >> OS: OpenSuse 11.0 kernal 2.6.25 i686 >> Java: jdk1.6.0_16 i386 >> Tomcat 6.0 (executed as a server in Eclipse Galileo) >> >> Thanks in advanced, >> >> Leon >> > > > -- > You receive this message as a subscriber of the [hidden email] > mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
One first step would be, when the lock occurs, to look at what the
threads are currently doing/waiting for. There are some ways to look at this. You can e.g. get a thread dump from the VM. -Erik On Tue, Jan 19, 2010 at 8:14 PM, Alessandro Vernet <[hidden email]> wrote: > Leon, > > These problems are hard to debug through the mailing list. In short: this > should not happen, and performance should not degrade in the way you > describe. But yes, we have already seen things like this, and they are in > general due either to an issue in your application, to a bug or something > sub-optimal in Orbeon Forms (which we fix when we find it!), or a > configuration issue. When it comes to configuration, see: > > http://wiki.orbeon.com/forms/doc/developer-guide/performance-tuning#TOC-Reduce-the-number-of-concurrent-pro > > Unfortunately, you can't configure Tomcat with maxThreads="3", but you can > do it with a front-end server. Just for the sake of testing this, could you > limit the number of concurrent thread in JMeter to 3? How do things work out > when you do that? > > Alex > > > > On Jan 11, 2010, at 10:23 PM, lmika <[hidden email]> wrote: > >> Sorry, I should mention that we are using Orbeon 3.7.1 >> >> Thanks, >> >> Leon >> >> >> On Tue, 2010-01-12 at 17:20 +1100, lmika wrote: >>> >>> Hi, >>> >>> While using JMeter to load test our application, which is deployed >>> separately from the Orbeon War in the same Tomcat, we have noticed that >>> when about 25 JMeter threads are requesting an XForm to be rendered, it >>> takes a number of seconds (around 30 or 40) for the request to be >>> handled. We have also found that over time, Orbeon stops handling these >>> requests and they time out. >>> >>> We have tried increasing the maximum heap size for Java to about 1 Gb >>> and reduced the "maxThreads" in Tomcat to about 10. >>> >>> Has anyone experienced this before? If so, do you have any suggestions >>> on where we can look or what we can change to fix the problem? >>> >>> The specs of our platform are: >>> >>> OS: OpenSuse 11.0 kernal 2.6.25 i686 >>> Java: jdk1.6.0_16 i386 >>> Tomcat 6.0 (executed as a server in Eclipse Galileo) >>> >>> Thanks in advanced, >>> >>> Leon >>> >> >> >> -- >> You receive this message as a subscriber of the [hidden email] mailing >> list. >> To unsubscribe: mailto:[hidden email] >> For general help: mailto:[hidden email]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws > > > -- > You receive this message as a subscriber of the [hidden email] mailing > list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |