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 845FE19B3A for ; Thu, 21 Apr 2016 08:15:46 +0000 (UTC) Received: (qmail 85740 invoked by uid 500); 21 Apr 2016 08:15:46 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 85683 invoked by uid 500); 21 Apr 2016 08:15:46 -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 85673 invoked by uid 99); 21 Apr 2016 08:15:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Apr 2016 08:15:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 02929C05EF for ; Thu, 21 Apr 2016 08:15:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 7qsjFQalVlBB for ; Thu, 21 Apr 2016 08:15:44 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6BB945F476 for ; Thu, 21 Apr 2016 08:15:43 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 8375025C8508 for ; Thu, 21 Apr 2016 01:02:05 -0700 (PDT) Date: Thu, 21 Apr 2016 01:01:37 -0700 (PDT) From: dmreshet To: user@ignite.apache.org Message-ID: <1461225697156-4407.post@n6.nabble.com> In-Reply-To: <1461181004178-4392.post@n6.nabble.com> References: <1461160828182-4375.post@n6.nabble.com> <1461181004178-4392.post@n6.nabble.com> Subject: RE: BinaryObject performance issue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I need BinaryObject to process ScanQueries on data with dynamic categories list. There are 30 different categories at current case. My Task is to calculate amount of persons in each category, so *map* is not working for me. try (QueryCursor cursor = cache.query(new ScanQuery((k, p) -> p.hasField(category)))) { for (Object o : cursor) counter += 1; } I see that it is possible to use another data structure: <(Long)CategoryId, List<(Long)PersonId>>. In this case my task will be calculated very fast. But this solution is very spesific for this task and I will not be able to reuse this data structure. So I want to undestand if I can use to solve this task, because it looks like more general solution. As you said that each update may be cause of metadata update I have do sort of categories before puch them to cache. It looks that it partialy helps, now it takes* 44 seconds *to put 5 000 elements in cache. Is there any way to improve performance? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-performance-issue-tp4375p4407.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.