Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 8974 invoked from network); 17 Mar 2005 18:16:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Mar 2005 18:16:37 -0000 Received: (qmail 31753 invoked by uid 500); 17 Mar 2005 18:16:35 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 31549 invoked by uid 500); 17 Mar 2005 18:16:34 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 31534 invoked by uid 99); 17 Mar 2005 18:16:34 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from mail21.sea5.speakeasy.net (HELO mail21.sea5.speakeasy.net) (69.17.117.23) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 17 Mar 2005 10:16:33 -0800 Received: (qmail 11024 invoked from network); 17 Mar 2005 18:16:30 -0000 Received: from dsl081-059-132.sfo1.dsl.speakeasy.net (HELO [172.16.31.104]) (pietro@[64.81.59.132]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 17 Mar 2005 18:16:30 -0000 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <974101869.1111064840683.JavaMail.jira@ajax.apache.org> References: <974101869.1111064840683.JavaMail.jira@ajax.apache.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Peter Molettiere Subject: Re: [jira] Updated: (AXIS-1771) Excessive Memory Use During Serialization/Deserialization Date: Thu, 17 Mar 2005 10:16:30 -0800 To: axis-dev@ws.apache.org X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Mar 17, 2005, at 5:07 AM, Davanum Srinivas (JIRA) wrote: > Try this out...tweaked options (including the streaming). Axis takes 8 > times slower consistently as compared to the ObjectOutputStream > option. Memory has reduced too. Let me know if you see something > screwy. I will try a bit more and report later. BUT am eager to hear > from you. I downloaded and ran your updated code, with a 32M max heap. It looks like it still takes more than 20M to serialize and deserialize a tree that takes less than a single megabyte in memory. It ran out of memory trying to serialize a 1844656 byte tree. Am I missing something here, or does this reflect the improvement you think your tweaks made? > Created tree with 5 levels and 3 children at each level > > Total memory usage: Created tree = 905 KBytes (926744) > Increase in allocation since last check = 905 KBytes (926744) > > Total memory usage: Serialized tree = 5 MBytes (5737504) > Increase in allocation since last check = 4 MBytes (4810760) > > Total memory usage: Deserialized tree. = 18 MBytes (19448264) > Increase in allocation since last check = 13 MBytes (13710760) > > > =========================================================== > > > Created tree with 5 levels and 4 children at each level > > Total memory usage: Created tree = 1 MBytes (1844656) > Increase in allocation since last check = -16 MBytes (-17603608) > - Out of Memory serializing. > > Process finished with exit code 1 -- Peter Molettiere Senior Engineer Truereq, Inc. http://www.truereq.com/