ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: Reaching Ignite's maximum throughput
Date Mon, 27 Aug 2018 16:32:45 GMT
Hello!

I imagine that serializable + pessimistic is not a very practical setting
from performance standpoint.

You want maximum guarantees there, so you will get the least performance,
and having a distributed system would not help you much in this case, if
not hinder.

Regards,
-- 
Ilya Kasnacheev


пн, 27 авг. 2018 г. в 19:24, Kia Rahmani <kiarash.rh@gmail.com>:

> Hey all,
>
> I have been playing with Ignite and studying how applications can be
> correctly optimized for it for a while now. However, I am having trouble
> witnessing *reasonable* transactional throughputs even in the baseline
> setting and I am wondering maybe I'm doing something fundamentally wrong
> (e.g. my current clients or workers' tasks are being serialized somewhere)
>
> For example, in my experiments (code attached) on a t2.2xlarge EC2 instance
> with 8 vCPU, consisting of a very simple read/write (counter increment)
> transaction (SERIALIZABLE + PESSIMISTIC), I fail to achieve a throughput
> above ~600 txns/sec with 16 concurrent Java threads (all connecting to the
> same Ignite client node running on the same machine)
>
> I would really appreciate it if you could help me understand the
> followings:
> Q1: Is the above number reasonable for Ignite transactional layer's maximum
> throughput? and if not,
> Q2: What am I doing wrong?
>
> Code Snippets:
> https://gist.github.com/Kiarahmani/2a49a0c0a512c99bfd65c69cce257aab
>
>
>
> Thanks a lot in advance!
> Kia
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Mime
View raw message