axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: [jira] Updated: (AXIS-1771) Excessive Memory Use During Serialization/Deserialization
Date Thu, 17 Mar 2005 22:13:41 GMT
Should i mark the bug as resolved? or take it off the blocker list? :)

-- dims


On Thu, 17 Mar 2005 14:06:25 -0800, Peter Molettiere
<pietro@axonstudios.net> wrote:
> 
> On Mar 17, 2005, at 12:48 PM, Davanum Srinivas (JIRA) wrote:
> > Try this one!!!!!
> 
> That is better... you've gotten it down to about a 4 to 1 ratio, which
> means the largest object graph you can de/ser in a 32M heap is about
> 4M. Execution speed seems largely unchanged though. A quick run (about
> 8 minutes) in JProfiler, just serializing and deserializing the same
> tree, doesn't reveal any leaks.
> 
> Lots better than before -- from a 20:1 to a 4:1 ratio -- a 5:1
> improvement. I'd take this bug off the blocker list.
> 
> --
> Peter Molettiere
> Senior Engineer
> Truereq, Inc.
> http://www.truereq.com/
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/

Mime
View raw message