3 ms·

That's disturbing. A quick Googling didn't find anything either way, can you provide a link that confirms this?

• tracker1 13y ago
  The whole point of the "cloud" is to use as commodity hardware as possible... accepting that failures happen. If you aren't using multiple regions and servers for deployment, with failover designs in your applications you are doing it wrong.
  • vardump 13y ago
    How do you suggest detecting corrupted memory that does not cause the instance to fail entirely, but silently corrupts your data or running processes? Or your page cache: https://blogs.oracle.com/ksplice/entry/attack_of_the_cosmic_rays1 https://blogs.oracle.com/ksplice/entry/attack_of_the_cosmic_...
    • AsymetricCom 13y ago
      I doubt that would cause an instance to fail entirely in a majority of instances. Linux has it's own memory corruption checking and fixing (on 64-bit words afaik), also the customer can code their own sanity checking or CRC data to detect and eliminate them as much as possible. Also, many file or copy operations have built in corruption checking as well. Of course, on top of that you have your virtualization platform which I'm sure has it's own series of sanity checks and complex hardware handling logic. Ultimately, it's a business decision of risk-management. Also, if you're in any kind of serious business like banking, there is already regulations around the standards of hardware/software you can use.
    • duaneb 13y ago
      Run n times, compare results. The idea of the same bit flipping twice is fairly ludicrous. These n times could be on the same machine, or distributed and compared with paxos. Then back everything up a billion times. Safety is extremely hard to guarantee, so the closest approximations will be expensive.
• deleted 13y ago
  [deleted]