I ran the Python test suite in Jython a while ago and monitored it with the GC MxBean. Memory consumption went up quite a lot throughout most of the test suite then. So looking into memory usage is definitely something we need to do before the next major release.

/Tobias

On Fri, Apr 11, 2008 at 12:22 AM, Leo Soto M. <leo.soto@gmail.com> wrote:
On Thu, Apr 10, 2008 at 5:34 PM, Frank Wierzbicki <fwierzbicki@gmail.com> wrote:
>  Upping the memory does fix it, so I guess I'll need to do that from
>  now on.  Sorry I should have thought of trying that -- I've just never
>  needed to before...

I encountered OOM errors when running the Django test suite too. And I
have not needed to add more memory on my DoJ attempts on the past
year.

It could be just Django tests growing large, but I think it's worth to
check if Jython's memory consumption has increased significatively
over the last months. I can check it, but no promises on when by now
:(

--
Leo Soto M.
http://blog.leosoto.com

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Jython-dev mailing list
Jython-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jython-dev