Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 17830 invoked from network); 18 Oct 2006 01:25:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Oct 2006 01:25:29 -0000 Received: (qmail 11797 invoked by uid 500); 18 Oct 2006 01:25:29 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 11570 invoked by uid 500); 18 Oct 2006 01:25:28 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 11559 invoked by uid 99); 18 Oct 2006 01:25:28 -0000 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of trustin@gmail.com designates 64.233.166.180 as permitted sender) Received: from [64.233.166.180] (HELO py-out-1112.google.com) (64.233.166.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2006 18:25:25 -0700 Received: by py-out-1112.google.com with SMTP id d80so133878pyd for ; Tue, 17 Oct 2006 18:24:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=PGVBuzAxKtbzZHR05VyEfGCGBbR7DVNQuYiDLXqnZGLlnBfhB+WsWvO2K116vPXDj/v80zvGewGeODyNjRcCpj00RCNJjNSRdCwGyyy+bQeR6R51IWRTE0mbScYA96PWlWQgABAM/hM+6Ub16vmxmwNRkmoSNqYTxrm+BvibtvE= Received: by 10.35.61.17 with SMTP id o17mr16531701pyk; Tue, 17 Oct 2006 18:24:04 -0700 (PDT) Received: by 10.35.68.13 with HTTP; Tue, 17 Oct 2006 18:24:04 -0700 (PDT) Message-ID: <768dcb2e0610171824x71be8608xe9e8adf6e654114f@mail.gmail.com> Date: Wed, 18 Oct 2006 10:24:04 +0900 From: "Trustin Lee" To: mina-dev@directory.apache.org Subject: Re: [mina] memory issues Cc: "Apache Directory Developers List" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1369_1117524.1161134644507" References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_1369_1117524.1161134644507 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Colin, MINA has its own mailing list. Please send an empty message to mina-dev-subscribe@directory.apache.org to subscribe to the list, and send your question to mina-dev@directory.apache.org from the next time. On 10/18/06, Colin Koeck wrote: > > I recently upgraded from netty2 to mina, and noticed mina is much more > stable which I am very happy about. However, it seems to be a memory hog > which concerns me a little. I'm trying to push about 75,000 messages, each > about 400 characters in length, through a client/server architecture using > mina..and the software throws a OutOfMemoryError about half-way through. > The only way I got it to successfully finish was to execute the software > with -Xmx1000M! > You will have to increase your direct buffer memory. Please refer to our FAQ page.: http://directory.apache.org/subprojects/mina/faq.html#connection-reset I think it might be a good idea to use heap buffers by default. What do you think, everyone? I'm going to profile the software later this week, but I'm wondering if the > results I got with mina are expected, and if there is any way to cut corners > and use less memory with mina. I'd appreciate it if anyone has any input on > the subject. Thank you. > Please let us know whenever you have any idea to improve MINA. All ideas will be appreciated. HTH, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6 ------=_Part_1369_1117524.1161134644507 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Colin,

MINA has its own mailing list.  Please send an empty message to mina-dev-subscribe@directory.apache.org to subscribe to the list, and send your question to mina-dev@directory.apache.org from the next time.

On 10/18/06, Colin Koeck < ckoeck@gmail.com> wrote:
I recently upgraded from netty2 to mina, and noticed mina is much more stable which I am very happy about.  However, it seems to be a memory hog which concerns me a little.  I'm trying to push about 75,000 messages, each about 400 characters in length, through a client/server architecture using mina..and the software throws a OutOfMemoryError about half-way through.  The only way I got it to successfully finish was to execute the software with -Xmx1000M!

You will have to increase your direct buffer memory.  Please refer to our FAQ page.:

http://directory.apache.org/subprojects/mina/faq.html#connection-reset

I think it might be a good idea to use heap buffers by default.  What do you think, everyone?

I'm going to profile the software later this week, but I'm wondering if the results I got with mina are expected, and if there is any way to cut corners and use less memory with mina.  I'd appreciate it if anyone has any input on the subject.  Thank you.

Please let us know whenever you have any idea to improve MINA.  All ideas will be appreciated.

HTH,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6 ------=_Part_1369_1117524.1161134644507--