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 B9448181B2 for ; Sat, 12 Dec 2015 00:08:19 +0000 (UTC) Received: (qmail 49109 invoked by uid 500); 12 Dec 2015 00:08:19 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 49066 invoked by uid 500); 12 Dec 2015 00:08:19 -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 49056 invoked by uid 99); 12 Dec 2015 00:08:19 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2015 00:08:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2E4CC180A9A for ; Sat, 12 Dec 2015 00:08:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 7o9o9U1ZWp06 for ; Sat, 12 Dec 2015 00:08:09 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 09F7321271 for ; Sat, 12 Dec 2015 00:08:09 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id C7A5D1C1EBAF for ; Fri, 11 Dec 2015 16:08:07 -0800 (PST) Date: Fri, 11 Dec 2015 15:58:28 -0800 (PST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1449878308323-2207.post@n6.nabble.com> In-Reply-To: <1449811504995-2202.post@n6.nabble.com> References: <1449654568773-2182.post@n6.nabble.com> <1449681300424-2188.post@n6.nabble.com> <1449722552428-2191.post@n6.nabble.com> <1449777544220-2197.post@n6.nabble.com> <1449811504995-2202.post@n6.nabble.com> Subject: Re: Need to effect cache at time of changes made in database MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kamesh, Here are my answers. 1. You should try loading the data in multithreaded fashion. The easiest way to do this is to extend CacheLoadOnlyStoreAdapter instead of CacheStoreAdapter and implement inputIterator and parse methods instead of loadCache method. This adapter will parallelize loading process automatically. Also if you have several nodes, you can speed up the process with partition-aware approach which is described in [1]. 2. Can you please clarify what you mean here? How objects are linked to each other? What behavior do you expect when you change one of them? 3. With Ignite you can execute any code on server nodes using Compute Grid [2]. Your tasks and/or closures can access data, so you will be able to do any required processing. Will this work for you? 4. No. Core functionality is the same in all editions, including third-party builds provided by GridGain. [1] https://apacheignite.readme.io/docs/data-loading#section-partition-aware-data-loading [2] https://apacheignite.readme.io/docs/compute-grid -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Need-to-effect-cache-at-time-of-changes-made-in-database-tp2182p2207.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.