Friday, April 03, 2020

Leaky time time.

Frank K woke up with a start. it was dark. he didn't usualy nap this long in the lab. he looked over at his lap top, and noticed the dashboard showed his cloud app was still using 80% of Azure's global compute resources. including FPGAs. and GPUs. and RDMA NICS. omg. what could it still be working on? he had all sorts of resource threshold kill switches - why was it still going.

hours later, having dismantled several data centers he was still none the wiser.
and where was his missing evening and half the night? that was another mystery.

he called up his old mate Mills - Dave was the ultimate clockmeister - he'd be able to figure it out.

he shared the dashboard window over zoom, and said "i'm stumped - what is it? where did all the  time go?"

dave asked him  to point his camera at the DAGv7 boards connected to the bus boys.

"there's your problem" dave said - "you've got counterfeit clocks running off FTL Italian Neutrinos."
"so what does that do" asked frank, ever humble at the feet and feats of the bearded guru.
"well, you know about space leaks, of course - thing of  the past now we write all our systems in rust. but that doesn't stop what we now call a time leak. but in this case, the measurement device has coupled the processing to a quantum clock which has altered the local manifold, so that time is slowed right down on the board, but speedup everywhere else nearby - its like offload, only the opposite. thank heavens you didn't wire it the other way, or there'd be very little left to do til we get to the big bang again. Next time, call me earlier" he offered, expansively.

No comments: