Hi, I've checked it on 4 nodes, stress test 15 minutes with 80% writes. Both reads and writes have improved in 5.2
READS/sec 247k -> 263k WRITES/sec 4547 -> 4771 (note: this is average, coordinator has about 2x more writes as it is the lock owner for all locks in replicated mode) that makes Paul, how many operations within transaction do you use? The results above are from single operation (put/get) per transaction (we have improvement in TRANSACTIONS/sec 5655 -> 5936 with this setting), I'll try to rerun with more ops/transaction as well. Radim ----- Original Message ----- | From: "Paul Ferraro" <[email protected]> | To: "Mircea Markus" <[email protected]> | Cc: "infinispan" <[email protected]>, "Paul Ferraro" <[email protected]> | Sent: Wednesday, May 1, 2013 5:05:39 PM | Subject: Re: [infinispan-dev] write-heavy performance degradation between 5.1 and 5.2 | | FYI - here's a summary of EAP 6.0 vs 6.1 performance: | https://bugzilla.redhat.com/attachment.cgi?id=741896 | | and here's the relevant BZ: | https://bugzilla.redhat.com/show_bug.cgi?id=956988 | | On Wed, 2013-05-01 at 15:55 +0100, Mircea Markus wrote: | > Hi Martin, | > | > Paul mentioned a severe degradation in performance between 5.1 and 5.2 for | > replicated + embedded + transactional + pessimistic caches, for | > write-heavy access. Do we have any tests we can run to check this? | > | > Cheers, | | | _______________________________________________ | infinispan-dev mailing list | [email protected] | https://lists.jboss.org/mailman/listinfo/infinispan-dev | _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
