[infinispan-issues] [JBoss JIRA] (ISPN-3102) Analyse the performance of MassIndexingTest
[
https://issues.jboss.org/browse/ISPN-3102?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-3102 at 5/15/13 7:41 AM:
--------------------------------------------------------------
Marking this as blocker as we need to investigate if the performance regression was
introduced in Infinispan 5.3 or it was present in 5.2 as well. If later, this
shouldn't stop the 5.3 release.
was (Author: mircea.markus):
Marking this as critical as we need to investigate if the performance regression was
introduced in Infinispan 5.3 or it was present in 5.2 as well. If later, this
shouldn't stop the 5.3 release.
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: Mircea Markus
Priority: Blocker
Fix For: 5.3.0.CR1, 5.3.0.Final
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