[infinispan-dev] New bundler performance

[Radim Vansa]

| > Seems that it's somewhat better (6050 writes/s) but not at the previous
| > level.
| what about the reads?

After Pedro's question I have tried to run ISPN-3221 fix with both old an new bundler (in configuration), and the result pretty surprises me as there should not be much of a difference (as all messages that are part of the test should be OOB => DONT_BUNDLE).

113842c8cf91cbb5a1bbd26e05fab7024fdec081 (last OK build)
new bundler: 1.5M reads/s, 7800 writes/s
old bundler: 1.3M reads/s, 4300 writes/s

73da108cdcf9db4f3edbcd6dbda6938d6e45d148 (removing DONT_BUNDLE)
new bundler: 1.2M reads/s, 4800 writes/s
old bundler: 150k reads/s, 250 writes/s

ISPN-3221 fix (Pedro's branch)
new bundler: 1.5M reads/s, 6050 writes/s
old bundler: 1.3M reads/s, 3100 writes/s

ISPN-3221 cherry-picked onto 73da108cdcf9db4f3edbcd6dbda6938d6e45d148
new bundler: 1.5M reads/s, 7800 writes/s
old bundler: 1.3M reads/s, 4300 writes/s

Radim

| > I am trying to cherry-pick it directly on the commit that failed it and see
| > where is the difference, then maybe I'll have to generate alternative
| > branch with ISPN-3221 commit after ISPN-2848
| > 73da108cdcf9db4f3edbcd6dbda6938d6e45d148 and iterate to next regression
| > origin.
| +1.
| > 
| > Pedro: I've noticed that in JGroupsTransport:577 you're changing the third
| > parameter of CommandAwareRpcDispatcher.constructMessage from false (as
| > found in 113842c8cf91cbb5a1bbd26e05fab7024fdec081) to true (as appears in
| > later commits), is this desired?
| 
| That has been changed on purpose to be true later on when fixing: ISPN-3043:
| Make synchronous backup calls use the OOB thread pool.
| 
| Cheers,
| --
| Mircea Markus
| Infinispan lead (www.infinispan.org)
| 
| 
| 
| 
| 
| _______________________________________________
| infinispan-dev mailing list
| infinispan-dev at lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/infinispan-dev
|