On 14 September 2011 20:16, Ted Dunning <ted.dunn...@gmail.com> wrote: > This is a red herring. No web server I know of restarts Java processes like > this. The JVM is kept hot and classes are not unloaded lightly.
True, but the server does not normally load all the classes in all its libraries, surely? In which case the first access to the FastMath class will incur the startup overhead. > A one minute startup due purely to this one library would be an issue. I > haven't heard that definitively demonstrated here at all. A micro-benchmark > would be useful. IIRC my tests showed something like 50ms for loading the FastMath class with the previous version. > On Wed, Sep 14, 2011 at 6:20 PM, Luc Maisonobe <luc.maison...@free.fr>wrote: > >> I see that a faster startup time would benefit an application required to >>> be restarted several times per second. But how realistic would that be? >>> >> >> This occurs in web services. This is a kind of application we get more and >> more often. I don't know at all how the server handles upcoming requests, >> and in particular if classes are reloaded or not, reoptimized or not. I know >> for sure the JVM is not restarted from scratch. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
