Subject: | |
From: | |
Reply To: | |
Date: | Wed, 26 Feb 2003 14:48:38 EST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
In a message dated 2/26/03 9:27:13 AM Pacific Standard Time,
[log in to unmask] writes:
> 10,000 CM to NM switches per second is *good* because it means your CM
> programs are getting a lot of work done. If you were to buy a system
> that's ten times faster than your current system, and the switch rate
> went up to 100,000/second, would you think that would provide even
> *more* justification for switching to NM because 100,000 is way worse
> than 10,000/second?
>
Ah! an ON topic item that I want to respond to! Gavin is making a very good
point! Measurements that are of the type qty over time sometimes seem bad
but might actually be good! In my mind, such measurements are neither "good"
nor "bad" - they are simply statistical measurements that should be evaluated
within their contecxt. A deeper understanding of what is going on inside the
code is necessary before taking some action based upon measurements.
Wayne
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|