• Subject: Re: What About Price vs. Performance?
  • From: "Nathan M. Andelin" <nathanma@xxxxxxxxx>
  • Date: Wed, 4 Apr 2001 21:46:14 -0600


The 100msec of CPU time for a 3.3KB dynamically generated web page sounds
right.  But the 20msec of CPU time to display a 5250 subfile is much higher
than what I expected.  Frankly, I expected your CPU to use about 5 msec to
build and display a screen with a subfile.  It takes my machine about 25msec
to build and display a screen with a subfile, and I thought you had a CPU
that was more than 5 times the speed of mine.

Maybe I'm missing something.


> ----------------------------------------------------------------------
> Date: Wed, 4 Apr 2001 18:05:02 -0500
> From: "Joe Pluta" <joepluta@PlutaBrothers.com>
> Subject: RE: What About Price vs. Performance?
> I did EXACTLY that, Nathan, two or three weeks ago.  I think I did 200
> pageup/pagedowns.  I got the following numbers:
> "A well written web application can serve up a 3KB dynamically generated
> page in about 100msec [of CPU time], as opposed to a green screen
> application outputting 1920 characters (or less) in about 20msec."
> About a 3-1 KB/sec ratio (or less).  Web was 30KB/sec, while green screen
> a little less than 100KB/sec (or maybe a lot less, because I doubt that it
> painted the entire screen on the pageup and pagedown).  Of course, I'll
> to do far more stringent testing than this to reduce the statistical
> but a 3-1 ratio isn't bad.
> 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

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].