• Subject: RE: Websphere: a resource hog?
  • From: "Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Thu, 24 May 2001 13:16:43 -0500

I agree that 30 seconds is acceptable.  But your machine is "tuned" for that
stuff (the newer processors, etc.).  My 720 isn't, as are most of the
machines where people complain of speed.  We still need our interactive CPW.
:)  It still takes me at least 3 minutes to start it up.  

Brad

> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
> Sent: Thursday, May 24, 2001 12:12 PM
> To: MIDRANGE-L@midrange.com
> Subject: RE: Websphere: a resource hog?
> 
> 
> By setting up different web servers, you can reduce the start 
> and stop time.
> And the machine you use is very important.  My cycle time for a server
> instance stop/start on my model 270 (this a machine with a 
> base price of
> $10,000) is a little over 30 seconds.  This is perfectly 
> acceptable for a
> development environment, where you shouldn't be making that 
> many classpath
> changes anyway.  If you're making lots of environmental 
> changes, then you're
> still in prototyping, you're not even in development, and you 
> should expect
> a little less throughput.  But once you've stabilized your 
> environment, your
> changes should be far smaller in scope, and the occasional 30 
> second turn
> around should be acceptable.
> 
> Joe
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.