Thanks, Ilya for your message.
I am aware of the cost of enforcing Serializability. What I am more
concerned about is if I am achieving Ignite's best or not? Specifically,
since I am not performing any replication and I have only one server right
now, I should be getting a performance somewhat clo
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.
The main reason I want to add backups is to allow very fast reads (assuming
backup reads are allowed).
Do you know of any way of keeping (stale) copies locally (next to the
clients) in order to save network latency in read operations, without
affecting write latency?
--
Sent from: http://apac
Thanks for the prompt reply!
Here is my client code:
https://www.codepile.net/pile/ywYXOvJX
In the experiment, the client resides in Singapore and 2 servers are located
at Singapore (same machine as the client) and Ohio. The primary copy is
maintained at Ohio and the backup is kept in Singapore n
Hi Folks,
WriteSynchronizationMode allows users to pick from 3 different
synchronization modes (FULL_SYNC, FULL_ASYNC, PRIMARY_SYNC) when performing
writes on a distributed setting.
Based on my understanding, when writing to the cache (whether inside or
outside of a transaction) the user-perceive
Hello all,
I recently started using Ignite for benchmarking a research project on a
local multi-node cluster. Now I need to deploy the cluster on geographically
distributed nodes, but I am stuck at setting up the connection on EC2
machines.
I have closely followed the TCP-based discovery instruct
