> It's amazing how many people jump into "optimisation" without having
> collected any metrics on their code first...
Similarly, it is astonishing to see how some people don't *look* at the
metrics. A long while back, I instrumented a chunk of UI code (using
Quantify, IIRC) which gave a "clear" indicator which function was
causing all the delays...
write()
Yes, there were a lot of writes to the display, but rewriting write on
an HPUX system wasn't really on. I probably spent more time explaining
to my manager why that wasn't a suitable target for optimising than I
did actually getting to the bottom of the problem.
My favourite optimisation was to take a min/max buffer function from a
run time of 5.5s to about 1.4ms (68030)... By rewriting the function so
that it wasn't splitting & copying buffers all over the place and made
use of pointers instead.
Peter
**********************************************************************
This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution
is prohibited. If you believe this message has been sent to you in
error, please notify the sender by replying to this transmission and
delete the message without disclosing it. Thank you.
E-mail including attachments is susceptible to data corruption,
interception, unauthorized amendment, tampering and viruses, and we
only send and receive e-mails on the basis that we are not liable for
any such corruption, interception, amendment, tampering or viruses or
any consequences thereof.
This email, its content and any attachments is PRIVATE AND
CONFIDENTIAL to TANDBERG Television, Part of the Ericsson Group.
www.tandbergtv.com
**********************************************************************
