4 ms·
It's like a meme in the world of trading: your system needs to survive for 24 hours, whatever happens after that - doesn't matter. This can really impact the
by alexeiz 4y ago
It's like a meme in the world of trading: your system needs to survive for 24 hours, whatever happens after that - doesn't matter. This can really impact the way you design the system. Ignoring memory leaks in C++, or outright disabling the GC in Java is one of the legit trade-offs you can make.
- Arrath 4y agoReminds me of the possibly apocryphal story of the missile whos guidance system had a memory leak. They profiled the memory leak and gave the chip enough RAM that it wouldn't fill up before the missile exploded. Problem solved!
- thfuran 4y agoThere are in service commercial planes that need to be routinely rebooted to prevent counters from overflowing, so I really wouldn't be surprised about similar sorts of issues in single use devices.
- snvzz 4y agoImagine the insanity of allocating memory mid-flight.
- saltcured 4y agoEarly in my career, before "turbo" or "boost" frequencies were a thing in commodity CPU products, I heard a similar tale about boosting the speed of the signal processors in a defensive radar system. The thought was that you would rather overheat and perform the calculation than protect the circuit and lose the ship. It's kind of a hail mary strategy. It definitely gave me a visceral feeling for how one should be ready to re-frame their systems analyses, even if apocryphal.
- mcspiff 4y agoThat’s common enough there’s a term for it: https://en.m.wikipedia.org/wiki/Battleshort https://en.m.wikipedia.org/wiki/Battleshort