A bit of discussion indicated that the trigger for the CPU spikes both times was our CEO logging in. We re-deployed to get a clean start, permanently banned him from the service, and moved on.
This is like finding a live grenade under your bed and putting it under the rug.
They found a way to reproduce a system killing bug, and instead of taking the time to understand it, they threw away their test case.
OP is definitely giving off white trash Daily Fail reader vibes.
Would be about $4000 worth of classy apparel.
Do you really think race is such a big part of it?
Didn’t people of colo(u)r build modern Britain?
I gasped when I saw this:
This is like finding a live grenade under your bed and putting it under the rug.
They found a way to reproduce a system killing bug, and instead of taking the time to understand it, they threw away their test case.
HONK!
How sampling error leads to incorrect conclusions, all in one map.
I’m on my alt today.