Sujet : Re: Solving thundering Herd with glibc...
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.lang.c++Date : 15. May 2025, 00:22:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <10038j8$2oarc$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : Mozilla Thunderbird
On 5/14/2025 8:05 AM, Vir Campestris wrote:
On 25/04/2025 09:37, Bonita Montero wrote:
Am 24.04.2025 um 23:33 schrieb Chris M. Thomasson:
>
"there’s no thundering herd, ever!" because a controlled test didn't "show it" is like saying race conditions do not exist because your code "worked fine this time."? Fair enough?
>
Yes, controlled test with 10'000 iterations.
The code is correct and trivial, but too much for you.
>
Once upon a time I put a race in a bit of code.
It took us 3 years to track down why our customers were reporting occasional faults :(
Oh shit. Damn. Did it "totally" deadlock once in a blue moon or just give out some bugged data to the customers? I hope it just deadlocked... Wow. Shit man. ;^o
(It turned out the trick to reproduce it was a combination of lots of CPU load and disk transfers not more than once every 30 seconds)
Yup. I have been there done that for some of my tests. I even put a bug in on purpose just to see how long it would take to trigger it... Decades ago. ;^o Sigh.
Solving thundering Herd with glibc...
Re: Solving thundering Herd with glibc...