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

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-1047:
--------------------------------

    Fix Version/s: 5.0.0.FINAL
                       (was: 4.2.2.BETA1)


Not sure this is a candidate for 4.2.2. Transactions are heavily revisited in 5.0: not only enhancements, bug fixes fixes as well.
Performance should be looked at post 5.0 stuff.

> 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: Mircea Markus
>            Priority: Critical
>              Labels: performance
>             Fix For: 5.0.0.FINAL
>
>         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