[JBoss Cache: Core Edition] - Re: Stress Tests
by manik.surtani@jboss.com
"jason.greene(a)jboss.com" wrote : The major memory increase is because of JBCACHE-1383, which creates 16 CHM segments and 17 locks per node. We have not yet done a 2.2 release that includes the fix, which is reducing it to 4. You could build the latest 2.2.x branch to try it.
2.2.0.CR7 is now available which does have JBCACHE-1383. You should see your heap size drop.
"jason.greene(a)jboss.com" wrote : The 3.0.0 Alpha release completely eliminates the problem (when using the MVCC locking mode). Perhaps you want to give that a try?
While you may not have the time to play with this, I would advise to at least keep it on your radar. It is _significantly_ faster than 2.X, and has a smaller memory footprint as well. I expect to release Alpha2 this evening/tomorrow morning, and my goal is to have this in GA by the end of September.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168522#4168522
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168522
17 years, 8 months
[JBoss Cache: Core Edition] - Re: Stress Tests
by manik.surtani@jboss.com
"lovelyliatroim" wrote : Just back to this question
|
| anonymous wrote :
| | I would have thought that having an ISOLATION level of NONE would turn out to be quicker but apparently not. What goes on behind the scenes when its set to "NONE"?.
| |
|
| Any ideas as to why it would perform better with an isolation level set compared to NONE??
|
| Thanks,
| LL
I suspect this has to do with the error levels you are seeing. With NONE, all access to the cache is unguarded. Which is good for memory (no lock objects, CHM segments, etc.) and *possibly* good for performance (if there is no contention). The moment there is contention you will start to see concurrent modification exceptions and this is possibly what JMeter is seeing as an error. You also need to look at how JMeter calculates this throughput - e.g., if it doesn't count erroneous connections as successful (i.e., remove from numerator), doesn't count them at all (remove from numerator and denominator) or adds the time taken to generate and throw an exception. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168521#4168521
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168521
17 years, 8 months