• Subject: Re: What About Price vs. Performance?
  • From: "Nathan M. Andelin" <nathanma@xxxxxxxxx>
  • Date: Thu, 5 Apr 2001 11:28:27 -0600

I think the 3-1 ration was a mistake, Jon.  I think the correct ratio was
30-1.  On a 460 CPW machine, it shouldn't be taking 25msec to read 20
records from a file, build a subfile, then display the result on a 5250
device.  For example, it takes my 300 Mhz Celeron PC only 4msec to read 51
records from a database table and copy them to another table.

If I correctly follow Joe Pluta's later comments, his earlier 5250 estimate
was too high.

Nathan.

-------- Original ----------------------

Date: Thu, 5 Apr 2001 10:44:42 -0400
From: Jon.Paris@hal.it
Subject: What About Price vs. Performance?

 >> Of course, I'll have to do far more stringent testing than this to
reduce the statistical error, but a 3-1 ratio isn't bad.

Actually it is a lot better than not bad.  Consider that (if my pricing
info is correct) that on most AS/400s a Batch CPU second is about a 6th to
a 10th of the cost of an interactive CPU seconds and you have the Web
application significantly outperforming the 5250.

Also we need to remember that CPU usage doesn't matter a hell of a lot
unless we're already using all we've got.  Most systems I've seen are not
constrained by CPU utilization.

-------End Original -----------------------




+---
| 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
+---

This thread ...


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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].