for the confusion.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5742.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-performance-improvements-tp5623p5710.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
-performance-improvements-tp5623p5709.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> wrote:
>
> Does OPTIMISTIC Serializable give better performance?
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5684.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Does OPTIMISTIC Serializable give better performance?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5684.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
d 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.
>
>
>
>
>
>
> --
&g
dding
> 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
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.
SYNC enabled, All our transactional caches are partitioned.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
