aditya mishra

If you use pounds instead of kilograms, I will hit you.

[aditya mishra @siighduuck]

Love this

[Omar Abdullah @OmarAbdullah]

Actually what is unfortunate is that with your blind lust to try to score cheap publicity points & please some people sitting across the border, you refuse to acknowledge that the IWT has been one of the biggest historic betrayals of the interests of the people of J&K. I have always opposed this treaty & I will continue to do so. Opposing a blatantly unfair treaty is in no way, shape, size or form warmongering, it’s about correcting a historic injustice that denied the people of J&K the right to use our water for ourselves.

[Jurassic World @JurassicWorld]

We see no possible way this could go wrong

[aditya mishra @siighduuck]

I miss Twitter the brand.

[McWar | Minecraft Server @McWar_Official]

After over a year in the making, the video is complete. Mojang has been caught breaking several European consumer protection laws & contract law that has resulted in thousands to suffer damages.

https://t.co/1Ax43KIqjR

[aditya mishra @siighduuck]

@MKBHD @YouTube Why did they make a youtube gaming rewind before a regular one

[aditya mishra @siighduuck]

@zatakster @MKBHD They are most certainly gonna do it all over again.

[aditya mishra @siighduuck]

Minimalist logo designs claimed their next target.

[aditya mishra @siighduuck]

@AutumnBlair_xo @MKBHD You're on to something here

[aditya mishra @siighduuck]

@code Can we just have the feature to see file size within the application without an extension please?

[aditya mishra @siighduuck]

@MKBHD If there ever was a product that had everything right, no one would talk about it. Think about it.

[Greg Kamradt @GregKamradt]

"You paid what for what?!?" - CFO @ OpenAI

[aditya mishra @siighduuck]

@picsthatg0hard_ It really said
S P R I T E

[aditya mishra @siighduuck]

Progress from 'beats 5%' to 'beats 100%' is satisfying.
https://t.co/s9AnNPaxoy

[Ben 🤖 @benfryc]

context switching

[Shaun Maguire @shaunmmaguire]

POV @SpaceX catching a rocket

[aditya mishra @siighduuck]

@CNviolations It's hilarious but I feel the note falls short on the 'unbiased language' part.

[aditya mishra @siighduuck]

Shouldn't 2021 be like a faulty year to compare with?

[ALX 🇺🇸 @alx]

Increases in Illegal Immigration populations in Swing States under the Harris/Biden Administration

[aditya mishra @siighduuck]

@KSI oh the irony

[aditya mishra @siighduuck]

Why did this appear on my feed RIGHT AFTER I'm finished watching the Three Body Problem...

[Peter Kraft @petereliaskraft]

What happens if your CPU gets something wrong? If it wakes up one day and decides 2+2=5?

Well, most of us will never have to worry about that. But if you work at a company the size of Google, you do, which is why this paper on "mercurial cores" is so fascinating.

What the authors report--and supposedly this is common knowledge at the hyperscalers--is that a couple cores per several thousand machines are "mercurial." Due to subtle manufacturing defects or old age, they give wrong answers for certain instructions. These can cause all sorts of impossible-to-diagnose issues. Some rare problems at Google that were traced back to bad CPUs include:

- Mutexes not working, causing application crashes
- Silent data corruption
- Garbage collectors targeting live memory, causing application crashes
- Kernel state corruption causing kernel panics

What makes CPUs go bad? It's very hard to tell. The authors posit that issues are becoming more frequent as CPUs get more complex, but there aren't solid numbers behind that. There are certainly strong relationships between frequency, temperature, voltage, and bad CPU behavior--most mercurial CPUs only cause problems under very specific conditions, but those conditions vary from CPU to CPU. Age is another source of problems, as older CPUs are more likely to exhibit problems.

Bad CPUs are an especially serious problem because they're very hard to detect. If cosmic rays flip bits in storage or on the network, that can be detected through error coding. But there's no analogy for a CPU that allows cheap online verification of its correctness. Instead, the best detection techniques involve monitoring for symptoms. If a core exhibits exceptionally high rates of process crashes or kernel panics relative to its fellows, that's a strong indication something is wrong with it. For the most critical applications, the authors propose triple modular redundancy--redoing each of its computations on three cores and majority-voting a reliable result.

More than anything, this paper is a call to action--letting everyone know that CPUs can fail. So now, if you ever find a bug you can't diagnose, you can blame the CPU! 🙂