Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73BBB180B9 for ; Tue, 19 Apr 2016 10:41:37 +0000 (UTC) Received: (qmail 33072 invoked by uid 500); 19 Apr 2016 10:41:32 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 33009 invoked by uid 500); 19 Apr 2016 10:41:32 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 32998 invoked by uid 99); 19 Apr 2016 10:41:32 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2016 10:41:31 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id DC789DFD7B; Tue, 19 Apr 2016 10:41:31 +0000 (UTC) From: bgutjahr To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis pull request: ARTEMIS-485: Use unbounded client t... Content-Type: text/plain Message-Id: <20160419104131.DC789DFD7B@git1-us-west.apache.org> Date: Tue, 19 Apr 2016 10:41:31 +0000 (UTC) Github user bgutjahr commented on the pull request: https://github.com/apache/activemq-artemis/pull/468#issuecomment-211852280 We use LInux and Windows, and we have seen consistent memory allocation. It's not stack memory. So far, I have found out that the memory is allocated in io.netty.buffer.PoolThreadCache instances. I have one instance per thread, each has allocate 216232 bytes in my test. I don't know yet if this is something I could influence in my application code. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---