[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1047) Cache performance slow in a JTA transaction with many cache operations

[Tom Waterhouse (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596266#comment-12596266 ] 

Tom Waterhouse commented on ISPN-1047:
--------------------------------------

The results look the similar for adding with one batch and with many smaller batches.

One batch:
[2011-47-18 10:47:14.44,  1357]INFO [main](TXCacheTest.java:81) - starting testWithOneBatch
[2011-47-18 10:47:14.71,  1384]WARN [main](arjunaI18NLoggerImpl.java:523) - ARJUNA-12130 Name of XA node not defined. Using Arjuna:1293
[2011-47-18 10:47:16.624,  3937]INFO [main](TXCacheTest.java:90) - testWithOneBatch complete - 2579ms <----

Many batches:
[2011-47-18 10:47:41.317,  3909]INFO [main](TXCacheTest.java:71) - 48000 test data batch added to cache
[2011-47-18 10:47:41.321,  3913]INFO [main](TXCacheTest.java:71) - 49000 test data batch added to cache
[2011-47-18 10:47:41.324,  3916]INFO [main](TXCacheTest.java:71) - 50000 test data batch added to cache
[2011-47-18 10:47:41.324,  3916]INFO [main](TXCacheTest.java:76) - testWithManyBatches complete - 2571ms <----

> Cache performance slow in a JTA transaction with many cache operations
> ----------------------------------------------------------------------
>
>                 Key: ISPN-1047
>                 URL: https://issues.jboss.org/browse/ISPN-1047
>             Project: Infinispan
>          Issue Type: Quality Risk
>          Components: Transactions
>    Affects Versions: 4.2.1.FINAL
>         Environment: Infinispan 4.2.1.FINAL/Hibernate 3.6.1.Final/Spring 3.0.5/JBossJTA 4.14.0
>            Reporter: Tom Waterhouse
>            Assignee: Manik Surtani
>            Priority: Critical
>              Labels: performance
>             Fix For: 4.2.2.BETA1
>
>         Attachments: ISPN-1047.zip
>
>
> When running Infinispan in a JTA transaction the performance of cache operations decreases as the number of operations increases in the transaction.  If adding to the cache, adding 50k items is much faster when done 1k items per transaction than all 50k in one transaction.
> Using JProfiler the bulk of the time was spent in LockingInterceptor.doAfterCall() for the all 50k in one transaction test.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira