https://issues.apache.org/bugzilla/show_bug.cgi?id=48358
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #2 from Mark Thomas <ma...@apache.org> 2009-12-10 09:22:47 GMT ---
As a point of clarification, if a JSP is changed then the old implementation
should be unloaded before the new implementation is loaded. Therefore, lots of
changes to a small number of pages shouldn't cause an issue. If such a scenario
does cause an issue then that is a bug and I would ask that you please open a
separate issue.
This enhancement appears to be addressing the use case where an application
consists of many thousands of pages that are rarely used so, in an effort to
conserve resources, pages that have not been accessed for a while are unloaded.
I can see how this could be useful in development, particularly if memory is
tight on an individual developer's machine. In production, I think it would be
easier (and give better performance) to spend few hundred dollars on some extra
memory for the server.
I also share Peter's concerns about the cost of the oldest JSP search and think
that this part of the patch needs to be revisited.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
