Hello, Growth loading CPU to 90% may caused by work of GC. For determine this you can get log and analyze log of GC [1]. Also you can use Unix utility for detection causes like dstat or top.
In further 50% CPU usage is maybe normal for your case (transaction OPTIMISTIC, READ _COMMITED). You can try to use OPTIMISTIC, SERIALIZABLE transaction, and retry if catch TransactionOptimisticException[2]. [1]: https://apacheignite.readme.io/docs/jvm-and-system-tuning [2]: https://apacheignite.readme.io/docs/transactions On Thu, Jun 16, 2016 at 2:06 PM, amitpa <[email protected]> wrote: > My transaction attributes now are OPTIMISTIC, READ _COMMITED. > > Avoided Transaction with the same key. > > Also when there is a lot of data Ignite seems to slow down due to Cache put > and get delays. I see the CPU load increases to 90%. is this due to > resizing > the cache? How can I optimize that? > > Lastly my CPU load is less than 50% when the transactions takes place (4000 > TPS). > > My Access point can take in 1 million per second so its not a bottleneck. > I > am expecting more than 5000 and for transactions to scale as I keep adding > nodes. > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5680.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
