But how much useful work do they do?
Mine's bigger than yours!
No doubt the sys-admins, managers and owning companies of all these exotically named 'pooters have a lovely time measuring each other up. With kudos and bragging rights being distributed accordingly.
The thing is, I can't help wondering how many of these giga, mega, tera flops (or even just "normal", non-floating point operations) actually go towards contributing to the numerical results these puppies presumably spend their days churning out. How many of these are consumed by the O/S, just keeping track of who's running which thread this precise microsecond, or which processor should handle the next interrupt from which piece of hardware. Or even simply unwinding stacks from all the subroutine / procedure / methods (depending on exactly which version of objectect-orientated FORTRAN-4 your application was coded in) that your highly elegant but operationally inefficient massively parallel visualisation uses, just so "the boss" can see a pretty screen to impress all his/her other bosses at the next measuring-up day.
We all know that software gets slower quicker than hardware gets faster. So are all these huge number of processors, the arcane architectures needed to squeeze utility from them, the operating systems they run and the highly optimising but too-hard-for-humans-to-understand compilers really producing the goods. After all, just how fast do you need to execute a gettimeofday() call?
