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 00:03:35 GMT
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 initialize distributed caches and load data from persistent store. Then the application
reads from and writes to caches.


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

    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?
    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=grCPTVl8FQVCiNf6dQwL5M3RP54gZKSIb-nKIoTtqh4&s=Zb6ay9er_YKcjzeqY9zeum4rf2rWCPnlYf9b_7wizXU&e=

View raw message