Wasn't there the story of an Army project from way, way back that had "impossible" specs for the performance and reliability of some component such as a relay?
Much time and money was spent engineering a solution that would meet these specs cycle after cycle with little success.
Eventually someone asked how many cycles the relay was expected to be used before replacement, and therefore, how long the relay had to be able to maintain those specifications.
The answer: Once.
There's always a balance to be struck, half the battle is figuring out where that balance is.
--
Lincoln King-Cliby, CTS
Applications Engineer
ControlWorks Consulting, LLC
V: 440.729.4640 x1107 F: 440.729.0884 I:
Crestron Authorized Independent Programmer
toggle quoted message
Show quoted text
-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Joseph K.Vossen
Sent: Friday, January 30, 2009 7:56 PM
To: Crestron@...
Subject: Re: [Crestron] Re: Comparing Time
[snip]
Way back in my Wang Labs days, the Performance Analysis group used to
laugh at the Operating Systems group for "optimizing the leap year
interupt." Makes me smile whenever I remember that gem.
LOL....
that reminds me of something that happend to me once. A guy I worked with
spent about 8 months tweaking a Linux network driver for high-performance; it
was being tested with a SmartBits chassis for high-volume throughput. He got
it to work fine (in the high-volume case), but customers were testing it
using ping(1) before rolling the box out in production and with that,
performance was terrible. I went back and spent about 3 weeks reworking the
driver to allow it to perform well in both low- and high-volume
traffic....some people spend way too much time on stuff that just doesn't
matter.
[more snip]
------------------------------------
Check out the Files area for useful modules, documents, and drivers.
A contact list of Crestron dealers and programmers can be found in the Database area.
Yahoo! Groups Links
