RE: memory profiling notes

Hello Dierk

200,000 sounds like a rather big number for a 50 lines script!
You can send anything you've found, that can be interesting for us.
The Parser will of course create a fairly good number of small objects, 
representing the tokens of the source being parsed. But well, perhaps 200,000 
is really too big ;-)
Please tell us what you found.

Thanks

PS: Well done for your Groovy integration :-), though unfortunately I haven't 
had the time nor the opportunity to play with :-(.

--
Guillaume Laforge
http://glaforge.free.fr/weblog


-----Message d'origine-----
De?: Dierk Koenig [mailto:dierk.koenig-vS5zOjhOW+wAvxtiuMwx3w@xxxxxxxxxxxxxxxx]
Envoye?: lundi 25 octobre 2004 15:51
A?: user-i9PBDF1N6cxnkHa44VUL00B+6BGkLq7r@xxxxxxxxxxxxxxxx
Objet?: [groovy-user] memory profiling notes


Hiall,

when doing some profiling on the Canoo WebTest project
I ran into some rather interesting memory 
numbers of the Groovy support. 
It looks like even for some simple script execution with
less than 50 lines of groovy code there are approx.
200'000 temporary objects created within Groovy.
Most of them seem to stem from the parser.

I understand that the Groovy project hasn't entered
the optimizing phase yet. If somebody is anyway
interested in the numbers I can provide more
detail.

I used the YourKit memory profiler.

cheers
Mittie