>>> Tim Stoop <[EMAIL PROTECTED]> 11-Aug-00 8:09:11 PM >>>
>This was the information I needed. At the moment we use
>lots of large servlets to handle doGet *and* doPost in one
>servlet. As I was comparing log files, I noticed that the
>servlets are kept in memory until they are used again.
>Therefor I started to wonder if it's practical to have them
>large and multi-functional (and of course because that
>way of programming isn't really Object Orientated).
Hmmm... the memory issue is not a good one to pick up on.
JVMs can garbage collect classes - so you will gain memory if you
seperate out the code.
However... for performance reasons you probably want to turn class GC
off.
The reason for that is two fold:
1. the less GC you have the more time your processor has to serve
requests
2. if you leave classes in memory they are quicker to instantiate
thus reducing request time
Most VMs offer a command line switch to turn off class GC.
Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
