ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Biren Shah <Biren.S...@servicenow.com>
Subject Re: get api takes more time when adding more nodes to cluster
Date Thu, 30 Nov 2017 01:39:40 GMT
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 will start another node in client mode on the same JVM? That does not to look
right. We don’t want to separate out these functionalities into different applications/JVM.

I can make read heavy caches to be replicated. That will improve get operations on those caches.
Ill try that out.


On 11/29/17, 5:07 PM, "vkulichenko" <valentin.kulichenko@gmail.com> wrote:

    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
    will see how it scales out.
    Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_&d=DwICAg&c=Zok6nrOF6Fe0JtVEqKh3FEeUbToa1PtNBZf6G01cvEQ&r=rbkF1xy5tYmkV8VMdTRVaIVhaXCNGxmyTB5plfGtWuY&m=q8E7KLmXbR4rdJjoAHbe2vqobCfu4moZki2hcqMjH6M&s=02J_1t0Q5IgCpjhUxcZsqyVJ3bOzlylkXdrdtB7Iw0Q&e=

View raw message