axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Molettiere <pie...@axonstudios.net>
Subject Re: [jira] Updated: (AXIS-1771) Excessive Memory Use During Serialization/Deserialization
Date Thu, 17 Mar 2005 18:16:30 GMT

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/


Mime
View raw message