ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Performance issue with REPLICATED cache
Date Tue, 27 Oct 2015 01:26:00 GMT
Hi Yuri,

Is there a chance you can create a small github project reproducing this?
You don’t need to have 15 caches, I think 1 cache would suffice.

If the above is not possible, then we will have to investigate by looking
at logs, code, etc., which would take more time.

D.

On Mon, Oct 26, 2015 at 1:22 PM, Yury Lazouski <yury_lazouski@epam.com>
wrote:

> Hi All,
> we are using Ignite 1.3.3 in win server environment.
>
> *Caches configuration*
>
> Each Ignite node has ~15 caches ~1M records each of Integer-to-Object
> entries (total memory required ~7Gb), configured as "REPLICATED",
> readFromBackup flag is set to "true", transaction mode is "ATOMIC", all the
> rest left defaults. One instance of loader service is configured which
> populates caches using IgniteDataStreamer on regular basis (scheduler) with
> deltas found in source DB, no other writes/updates are performed on caches,
> from client perspective cache is effectively read-only. For the sake of
> experiment simplification database is getting loaded to caches only once -
> no further updates are happening.
>
> *Job execution*
>
> In-process (same jvm) client submits callable task to Ignite node which
> essentially traverses caches via get(key) and does calculations on
> retrieved
> data.
>
> *Problem*
>
> With one Ignite node average get(key) operation time is 20-40 μs, with
> enabling second node timings (same local node timings!) are getting
> increased to >100 μs. With adding parallel clients (parallel execution of
> callable tasks which travers same caches) numbers reach millisecond level.
> If we configure loader service on each node and switch mode to "LOCAL",
> get(key) time is constant (0-1 μs) and performance scalability is linear
> with addition of Ignite nodes. So the question is how to make "REPLICATED"
> cache perform like "LOCAL" if there are no updates to the caches and data
> is
> only getting accessed locally? Please advise.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-with-REPLICATED-cache-tp1710.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Mime
View raw message