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 F3A5B200C4F for ; Sat, 18 Mar 2017 03:46:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F23B0160B8C; Sat, 18 Mar 2017 02:46:32 +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 480A4160B80 for ; Sat, 18 Mar 2017 03:46:32 +0100 (CET) Received: (qmail 94975 invoked by uid 500); 18 Mar 2017 02:46:31 -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 94964 invoked by uid 99); 18 Mar 2017 02:46:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Mar 2017 02:46:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E9BC6C6680 for ; Sat, 18 Mar 2017 02:46:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4lJsv7Kul3ax for ; Sat, 18 Mar 2017 02:46:30 +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 9B6C35FB79 for ; Sat, 18 Mar 2017 02:46:29 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id C56EE3F11A8E for ; Fri, 17 Mar 2017 19:22:00 -0700 (PDT) Date: Fri, 17 Mar 2017 19:46:27 -0700 (MST) From: lawrencefinn To: user@ignite.apache.org Message-ID: <1489805187757-11292.post@n6.nabble.com> In-Reply-To: References: <1489696124205-11252.post@n6.nabble.com> <1489763845901-11285.post@n6.nabble.com> Subject: Re: destroy and offheap memory MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Sat, 18 Mar 2017 02:46:33 -0000 Im just measuring the memory used by the ignite pid (using top or whatever unix command). I built a test app trying to reproduce this on my laptop by loading a lot of data and then destroying it. I repeat this a few times and the process goes back down to the same memory and works as expected. But our real app seems to not go back down in memory. Are there other things that could possibly lead to memory leaks? Using onheap cache? Maybe no closing a datastreamer or cursor? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/destroy-and-offheap-memory-tp11252p11292.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.