Also for profiling failures in meeting minimum performance constraints...

rwilhm — Wed, 21 May 2008 02:39:55 GMT

I find measurements like "FPS" (gauche and broad-stroke though they may be) more useful in isolating violations of performance thresholds in the fine tuning stage than in implementation optimization... Looking for poor performance, and then check-pointing the in-flight load impacting the performance load relative systems. Catching exceptional, unanticipated systemic scenarios/states "in the act" for forensic analysis has it's place.

To use the metaphor, once we have a reasonably-performing haggis factory, we want to know when the production line spontaneously sputters to a stall/halt, and be able to inspect the line to find out why.

(If the point of the original post was to question the value of basing design/implementation decisions "predictively" from aggregated metrics at runtime... I'm not arguing against that. If anything, the same is true in the application of profiling that I outlined: You can't predict the problem potential of a system from derivative metrics without capturing the underlying state of the actors in the system.)

re: A tale of many haggis

trayle — Sat, 24 May 2008 15:16:05 GMT

Mmm. Haggis. Cough Cough. <Loud Wretching>

Cough Cough.

I'm okay those Rocky Mountain Oysters I just ate almost came up though.

re: A tale of many haggis

deviruchi — Sat, 18 Oct 2008 13:10:38 GMT

I too got bogged down in such haggis-related tomfoolery.

Not only have I learned a lesson today, but I am now going to buy a haggis.