We have a number of customers for which we are managing Tomcat servers
on their own Midrange boxes (to run the web extension of our CRM product).
Differences in context deployment speeds is of course, in part, a
function of how long it takes to get a 101M WAR file onto their machine.
But that wouldn't be a factor in undeployment, nor in starting or
stopping a context.
And we're finding wide variations in those speeds: sometimes, a matter
of seconds, and sometimes you could go out and get coffee -- at the
Starbuck's around the corner -- and find that it's still processing.
Sometimes, we'll see variations this extreme on boxes that are at least
theoretically the same model. We've put Tomcat into its own subsystem,
with its own private pool, and "throw memory at it," with little or no
improvement in speed, and sometimes, we've seen boxes that look tiny and
underpowered give quicker responses than big heavy-duty models.
Anybody have any suggestions we haven't already tried?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.