User development, A new message was posted in the thread "JBoss Cache usage: direct gets vs ordinary gets": http://community.jboss.org/message/532467#532467 Author : Alex Reshetnyak Profile : http://community.jboss.org/people/areshetnyak Message: -------------------------------------------------------------- Hi, Manik Surtani. Thanks for the quick responseю   We was tested our Query benchmark with eviction wakeup interval equal 500 and 2000. Result of Query benchmark with different  eviction wakeup interval : Threads                      1                              2                              3                                  4 300threads   ~407tps      ~458tps      ~1947tps       ~2593tps 1. JBoss Cache-based configuration (current one) with wakeUpInterval="2000". 2. JBoss Cache-based configuration (current one) with wakeUpInterval="500". 3. JBoss Cache-based configuration (current one) with wakeUpInterval="2000", but with patched jcr.core, using peek/getDirect methods. 4. JBoss Cache-based configuration (current one) with wakeUpInterval="500", but with patched jcr.core, using peek/getDirect methods. After  drop eviction wakeUpInterval to 500, we have increase performance to :   - JCR (non patched)   :  ~12% - JCR (patched jcr.core, using peek/getDirect methods)  ~33% [ https://jira.jboss.org/jira/browse/EXOJCR-545 ] https://jira.jboss.org/jira/secure/ViewProfile.jspa?name=areshetnyak - 17/Mar/10 06:44 AM The test SearchNodesByPropertyTest was checked with eviction wakeup interval equal 500 and 2000.  Result of Query benchmark with different  eviction wakeup interval :  Threads             1                    2                    3                      4 300threads   ~407tps      ~458tps      ~1947tps       ~2593tps  1. JBoss Cache-based configuration (current one) with wakeUpInterval="2000". 2. JBoss Cache-based configuration (current one) with wakeUpInterval="500". 3. JBoss Cache-based configuration (current one) with wakeUpInterval="2000", but with patched jcr.core, using peek/getDirect methods. 4. JBoss Cache-based configuration (current one) with wakeUpInterval="500", but with patched jcr.core, using peek/getDirect methods.  After  drop eviction wakeUpInterval to 500, we have increase performance to :  - JCR (non patched)   :  ~12% - JCR (patched jcr.core, using peek/getDirect methods)  ~33% -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/532467#532467