Biren,
I meant that you can have a standalone cluster and embed client node into
the application instead of server node. Making these caches replicated can
be also an option - in this case all reads will be local and fast.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I am not sure how client-server deployment would look in our case. Our
application starts the ignite in server mode, initializes caches and later
access those caches. To switch to client-server deployment, the application
will start a node in server mode, initializes caches. Then the application
Biren,
If half of your operations became multiple times slower, why would you
expect throughput to increase? In case you don't use collocation, I would
recommend you to switch to client-server deployment. Initial performance
with two nodes and fully replicated cache can be slower than now, but you
Well I am not expecting that by doubling the number of nodes, I will get 2x
throughput. But it should be at some liner rate and definitely should not bring
the throughput down. We have embedded the ignite in the application. On start
of the application we start ignite in server mode. We initiali
Biren,
That's a wrong expectation because local in-memory read is drastically
faster than a network read. How do you choose a server node to read from?
What is overall use case?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Val,
We are doing read on server only. I understand the get will be slow in case of
4 nodes because its doing remote get for some cache entries. But it should not
bring down overall throughput of an application. Just to give you some context,
with 2 nodes the application can process 500K dat
Hi Biren,
Are you doing reads from a client or directly on server nodes? If the
letter, then I guess you just do not collocate properly. With two nodes and
one backup all data is available on both nodes, so any server side read
would be local. With four nodes some of them would be remote which is
Hi,
On adding more nodes to the cluster, the get api slows down. I have a cache
with 2 million entries. The cache gets loaded at the start of the cluster and
does not change frequently. Here is the cache configuration. I had start the
cluster with 2 nodes and added 2 more nodes later on.
CacheC
