3 ms·
If you don't mind me asking, what kind of workload requires this kind of "high-availability shenanigans". Sounds fascinating.
by dj_gitmo 4y ago
If you don't mind me asking, what kind of workload requires this kind of "high-availability shenanigans". Sounds fascinating.
- hamandcheese 4y agoIf RDS could fail over in 1ms I would be extremely happy. In practice, a few minutes of downtime for things like DB upgrades is usually acceptable in the business I am in, however this is enough time to cause quite a lot of alerting noise. If the window of unavailability was instead 1ms, there would be dramatically less noise, potentially none.
- dinosaurdynasty 4y ago9-1-1 callcenters often do, some use specialized server hardware that can in <1ms switch from one motherboard/CPU to another when it fails. Apparently there are some workloads in finance that use similar hardware.
- ale42 4y ago> Apparently there are some workloads in finance that use similar hardware. Not surprising, I've heard from someone who worked at a financial institution doing high-speed trading that basically every ms counts for them.
- touisteur 4y agoEvery microsecond, and HFT people rent datacenter space the closest possible to physical exchanges... When speed of light is your main concern, maybe the Linux kernel is not your friend anymore (although dpdk can help here). I'm happy people keep pushing the kernel so hard, and still try to keep the kernel generic and composable, so we can profit from this huge, amazing work.
- touisteur 4y agoOften times it's mission critical systems where latency is key, for many reasons: - you have a human in the loop to take a split second decision, every millisecond counts - you have a very short time to perform 'looped' operations - where the result of one measurement must be taken into account to effect the next measurement (adaptive optics, some radar systems, some mechanical control loops) and you can't wait. You'd think 'oh but you got more than 1 ms for that' Well not always since one must take into account the time to detect the failure, and the time to switch other parts of the system (which sometimes must be done in sequence with the connection takeover). I'd say 'forget tcp' there but we don't always get to decide the comm layer...
- u8080 4y agoSuch redundance shenanigans used in Cellular networks, single node could handle thousands calls at the same time.