Hello, Can you please clirify transaction attributes? If I remember correctly it was PESSIMISTIC, REPEATABLE_READ [1]. Why do you use exactly this type of transaction?
When you using transaction by same key, they can blocked each other. Also need check network and CPU loading when your application running. Why do you think 4000 TPS is a bad performance? Maybe executing transaction will line up on concurent acces to same keys. For further investigation will need to see test cases, which demonstrate issue. [1]: https://apacheignite.readme.io/docs/transactions On Tue, Jun 14, 2016 at 6:59 PM, amitpa <ami...@nrifintech.com> wrote: > We are getting 4000 TPS with 10 caches on C4 $x large AWS instance. With > two > nodes on the same machine. Each transaction updates around 8 partioned > cache . > > We have given large heap but still we see the cache updates get slower with > static data. is there any work around for this? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5632.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
