Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D063118B0B for ; Wed, 14 Oct 2015 21:30:18 +0000 (UTC) Received: (qmail 84036 invoked by uid 500); 14 Oct 2015 21:30:18 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 83992 invoked by uid 500); 14 Oct 2015 21:30:18 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 83983 invoked by uid 99); 14 Oct 2015 21:30:18 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Oct 2015 21:30:18 +0000 Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 656A01A031E for ; Wed, 14 Oct 2015 21:30:18 +0000 (UTC) Received: by oiar126 with SMTP id r126so35603561oia.0 for ; Wed, 14 Oct 2015 14:30:17 -0700 (PDT) X-Gm-Message-State: ALoCoQkBaniGs7WMVHiljQwpoipMF/SBhQqiEuf94JabIUW/aCT/ZIC/mY0W8/w/KGNrDRkPyy/s X-Received: by 10.202.86.214 with SMTP id k205mr3286677oib.115.1444858217694; Wed, 14 Oct 2015 14:30:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.223.67 with HTTP; Wed, 14 Oct 2015 14:29:38 -0700 (PDT) In-Reply-To: References: <1444660523442-1589.post@n6.nabble.com> <1444810750914-1608.post@n6.nabble.com> From: Dmitriy Setrakyan Date: Wed, 14 Oct 2015 14:29:38 -0700 Message-ID: Subject: Re: CacheStore servicing multiple requests for same key To: user Content-Type: multipart/alternative; boundary=001a113d841ad11a79052217447f --001a113d841ad11a79052217447f Content-Type: text/plain; charset=UTF-8 On Wed, Oct 14, 2015 at 6:59 AM, Alexey Goncharuk < alexey.goncharuk@gmail.com> wrote: > Ignite already has this functionality, it is implemented in > CacheStoreBalancingWrapper. All concurrent loads with the batch size up to > loadAllThreshold are tracked and only one request is issued to the > underlying store. The reason for this differentiation is that multi-key > loads require additional overhead and it is more beneficial not to track > these loads starting from some batch size large enough. > > However, it turns out that there is no way to configure this threshold. I > created a ticket for it: https://issues.apache.org/jira/browse/IGNITE-1681 > > Folks, can you review the suggested way of configuring this parameter? > (described in the ticket). Once the community agrees on the ticket, it will > be fairly easy to fix and I think it is a good point to start contributing > to Ignite :) > Alexey, Are you sure you are talking about the same functionality? It looks like the ticket is filed for loadAll() calls only. How about multiple load() calls for the same key from different threads? D. View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-servicing-multiple-requests-for-same-key-tp1589p1608.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > --001a113d841ad11a79052217447f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Oct 14, 2015 at 6:59 AM, Alexey Goncharuk <= ;alexey.gon= charuk@gmail.com> wrote:
Ignite already has this functionality, it is implemented in = CacheStoreBalancingWrapper. All concurrent loads with the batch size up to = loadAllThreshold are tracked and only one request is issued to the underlyi= ng store. The reason for this differentiation is that multi-key loads requi= re additional overhead and it is more beneficial not to track these loads s= tarting from some batch size large enough.

However,= it turns out that there is no way to configure this threshold. I created a= ticket for it: https://issues.apache.org/jira/browse/IGNITE-1681<= div>
Folks, can you review the suggested way of configuring t= his parameter? (described in the ticket). Once the community agrees on the = ticket, it will be fairly easy to fix and I think it is a good point to sta= rt contributing to Ignite :)

<= /div>Alexey,

Are you sure you are talking about the same= functionality? It looks like the ticket is filed for loadAll() calls only.= How about multiple load() calls for the same key from different threads?

D.=C2=A0

View this message in context: http://apache-ignite-users.705= 18.x6.nabble.com/CacheStore-servicing-multiple-requests-for-same-key-tp1589= p1608.html
Sent from the Apache Ignite Users mailing list archive at Nabble.= com.


--001a113d841ad11a79052217447f--