Eclipse Foundation offers a free profiler, not sure all that it does (have
only had a chance to look at it quickly). It is the TPTP project (Test and
PerformanceTools Platform). http://www.eclipse.org/tptp/
NetBeans offers one as well. http://profiler.netbeans.org/
Also AppPerfect Standard Edition http://www.appperfect.com
So don't say you don't have one now :-)
----- Original Message -----
From: "p green" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Wednesday, October 19, 2005 5:49 AM
Subject: Re: Getting to 4.0 end game
The issue of memory leaks. I was definitely running on a system with
caching enabled. Unless there is another way to disable the cache
other than using the argument:
-Dorg.apache.tapestry.disable-caching=true
I do not mind admitting to stupid mistakes (we all make them) but I
am sure the cache was enabled on two non-development systems which
failed with OutOfMemoryError's. Both were running tomcat 5.0 one was
a Linux system and the other was a Windows XP system.
They failed when rendering the same page repeatedly with the data.
This page was very large (i.e. 5000 rows of 9 columns). I changed
this page to only render a maximum of 100 rows.
I have not done any further tests and never ran a profiler over the
code (because I do not have one).
I do not want to send you on a wild goose chase but I still think
there could still be an issue here.
Paul
On 16 Oct 2005, at 16:24, Howard Lewis Ship wrote:
I believe we are getting very close to the 4.0 end game.
I still have a few bugs I really want to fix, and some more
documentation and tutorials that *should* get written. But nothing
that can't wait for a 4.0.1 bug fix release or a 4.1 release.
I would encourage developers to take a look at the open bug list and
see what's pending.
How many people are using 4.0 in a production environment right now?
Or ramping up to a production environment?
My biggest concern is runtime performance. My gut feeling is that
outside of startup time, 4.0 is equal to or better performing than
3.0. I've been troubled by some concerns on the web about memory
leeks possibly related to Javassist class creation (but I suspect
those people are running with caching disabled and just don't know it,
or won't admit it).
I'm hoping that beta-12 will be the last beta, and we can call a vote
for a release candidate after that. However, release working software
is more important than keeping to a schedule.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
