Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B884E200D0E for ; Tue, 26 Sep 2017 17:20:24 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B6EFD1609B4; Tue, 26 Sep 2017 15:20:24 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 085EB1609C1 for ; Tue, 26 Sep 2017 17:20:23 +0200 (CEST) Received: (qmail 17861 invoked by uid 500); 26 Sep 2017 15:19:43 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 17777 invoked by uid 99); 26 Sep 2017 15:19:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 15:19:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E25FF1A04D2 for ; Tue, 26 Sep 2017 15:19:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.485 X-Spam-Level: *** X-Spam-Status: No, score=3.485 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 8seqiL_AyetJ for ; Tue, 26 Sep 2017 15:19:40 +0000 (UTC) Received: from n4.nabble.com (n4.nabble.com [162.253.133.72]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 688B95F5FD for ; Tue, 26 Sep 2017 15:19:40 +0000 (UTC) Received: from mben.nabble.com (localhost [127.0.0.1]) by n4.nabble.com (Postfix) with ESMTP id BF45F148C670E for ; Tue, 26 Sep 2017 08:19:39 -0700 (MST) Date: Tue, 26 Sep 2017 08:19:39 -0700 (MST) From: endianignite To: dev@ignite.apache.org Message-ID: <1506439179781-0.post@n4.nabble.com> Subject: Per-entry overhead - some questions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 26 Sep 2017 15:20:24 -0000 Hi Igniters, I have been looking in to the per-entry overhead for Ignite cache entries and have a couple of questions. 1. Does each GridCacheMapEntry require a reference to GridCacheContext or could this field be removed/optimized in some way? Is the GridCacheContext instance the same for every entry in a particular cache? 2. Is the GridCacheMapEntry extras field (a reference to GridCacheEntryExtras) often/usually null? If so, could we find a clever way to remove this field and save a further 8 bytes? The reason for asking is that I am looking at a use-case where object sizes are very small, but the number of objects is very large, and therefore the overhead is substantial. In this particular case, the overhead is 70-75% of the consumed memory. I look forward to hearing your thoughts. Regards Mike -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/