Hi,
We are trying to run performance test on our application. Until now we've done the following. Ran 30 simultaneous threads (users) on JMeter and found that the CPU spikes consistently at around 90%. We fine tuned most of the parameters like using gzip compression, increased the memory of tomcat (currently its 3GB physical memory), cache all css, images and js files, increased the xforms.cache.size values. An analysis using samurai thread dump tool shows that orbeon is trying to lock threads related to MemCache "http-61-28" daemon prio=10 tid=0x0000000001e91800 nid=0x1419 waiting for monitor entry [0x00007f3d50492000] java.lang.Thread.State: BLOCKED (on object monitor) at org.orbeon.oxf.cache.MemoryCacheImpl.findValid(MemoryCacheImpl.java:167) - waiting to lock <0x0000000772144b30> (a org.orbeon.oxf.cache.MemoryCacheImpl) I've attached the thread dump along with the tool here. Kindly let me know what is orbeon trying to do or where am I going wrong. Thanks --SD |
Administrator
|
It's been a while but another user had what seemed like a cache
contention issue a while ago (pre-3.9). One suspicion was that it was the XPath cache's fault, but that was not the only thing involved in that application and eventually it seemed that the issue disappeared. At the time we started prototyping using using ConcurrentHashMap to back MemoryCacheImpl. That might be something to try out. Also in July 2010 this change (which is in 3.9 and 4.0) was designed to help with that kind of things by using smaller keys in the cache: https://github.com/orbeon/orbeon-forms/commit/d3e588e47f50d4af5574c2cb5070c0698ae805e6#diff-9 Are you using 3.9? -Erik On Thu, Jul 5, 2012 at 4:12 PM, SD <[hidden email]> wrote: > Hi, > > We are trying to run performance test on our application. Until now we've > done the following. > Ran 30 simultaneous threads (users) on JMeter and found that the CPU spikes > consistently at around 90%. We fine tuned most of the parameters like using > gzip compression, increased the memory of tomcat (currently its 3GB physical > memory), cache all css, images and js files, increased the xforms.cache.size > values. > > An analysis using samurai thread dump tool shows that orbeon is trying to > lock threads related to MemCache > > > > I've attached the thread dump along with the tool > http://orbeon-forms-ops-users.24843.n4.nabble.com/file/n4655434/catalina.zip > here. Kindly let me know what is orbeon trying to do or where am I going > wrong. > > Thanks > --SD > > -- > View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Performance-Problem-tp4655434.html > Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com. > > > -- > 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 |