[infinispan-issues] [JBoss JIRA] (ISPN-3102) Analyse the performance of MassIndexingTest
Adrian Nistor (JIRA)
jira-events at lists.jboss.org
Wed Oct 2 07:34:03 EDT 2013
[ https://issues.jboss.org/browse/ISPN-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12808862#comment-12808862 ]
Adrian Nistor commented on ISPN-3102:
-------------------------------------
I've tried running this test (with all logging set to WARN) on 5.3.x, 6.0 and on the exact revision when the test was added. The results were nearly identical for all runs: 1.5 mins. So this is not a regression. Still, indexing 2000 entries in 1.5 mins is very slow...
> Analyse the performance of MassIndexingTest
> -------------------------------------------
>
> Key: ISPN-3102
> URL: https://issues.jboss.org/browse/ISPN-3102
> Project: Infinispan
> Issue Type: Task
> Reporter: Mircea Markus
> Assignee: Adrian Nistor
> Priority: Blocker
> Fix For: 6.0.0.CR1
>
>
> MassIndexingTest runs on CI in 10 mins with TRACE on and 3 mins with TRACE off. According to Sanne this shouldn't take that long:
> {quote}
> sannegrinovero
> 11:50 mmarkus: the org.infinispan.query.distributed.MassIndexingTest test is adding 2000 entries to the cache. True that might be a bit excessive, still if it takes 10 minutes you have a problem in Infinispan core.
> mmarkus
> 11:52 sannegrinovero: each such write is indexed I take it?
> sannegrinovero
> 11:53 mmarkus: no: withFlags(Flag.SKIP_INDEXING)
> 11:54 mmarkus: but it's a 4 node DIST test using Map/Reduce.
> sannegrinovero
> 11:54 then the Map/Reduce job does some indexing but the indexing engine didn't change overnight
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list