The title says it all; I've been greatly amused today reading his column in
the java performance tuning newsletter... but can it possibly be real? It
reads like a combination of Dilbert and Adrian Mole's diary.. for instance:

June 6. It's not a myth. Well not any more. Did you ever hear about the
enterprise system which the developers put in pauses so that they could take
them out later to make the system faster? Actually, the way I hear it is
that they anticipated that as the system scaled up, the load would increase
and slow the system down, so they put in configurable sleep statements that
slowed the system when they first deployed. Then, when it started getting
loaded, they wound down the sleeps. Apparently, they kept the system running
at roughly the same performance even after it went to full company-wide
release. I always thought this was yet another urban myth. But now I've
implemented the myth. Yes, my code tweaks way exceeded my 50% target
speedup, so I added in sleep code. That way, next time I come to tune, I can
either speedup the system real quick (and look so good), or take my time and
doodle. Had to put the sleeps into the monitoring code so that no one else
finds them, but that's good, one nice central place.

..that's from one of his earlier entries. I guess I should be thankful that
this doesn't sound like anything I've encountered yet.

Does anyone else know anything more about this guy?

Fritz

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CTJUG Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/CTJUG-Forum
For the ctjug home page see http://www.ctjug.org.za
-~----------~----~----~----~------~----~------~--~---

Reply via email to