Re:Garnet – A new remote cache-store from Microsoft Research
by robertlagrant on Tuesday March 19, 2024 @09:34AM
(#39755574)
DNS, BGP, or branch prediction. Pick three.
Re:Garnet – A new remote cache-store from Microsoft Research
by zimpenfish on Tuesday March 19, 2024 @10:31AM
(#39756111)
Stealing from the greats, "DNS, BGP, off-by-one errors, or branch prediction. Pick three."
Re:Garnet – A new remote cache-store from Microsoft Research
by jakopo87 on Wednesday March 20, 2024 @01:41PM
(#39769789)
It was off-by-one, indeed.
Re:Garnet – A new remote cache-store from Microsoft Research
by donbreo on Wednesday March 20, 2024 @04:52AM
(#39764105)
I just faced an issue with redis this week. It was causing my Javascript heap memory to go bust. I thought it was a data leak in my code but it turns out the redis client was filling it up and I fixed it by simply adding a static delay every 1 million set operations so that the garbage collector had enough time to do its job. (I was stress testing for a total of 6 million set operations)
Re:Garnet – A new remote cache-store from Microsoft Research
by AlexeyBelov on Thursday March 21, 2024 @03:07AM
(#39775571)
That's an issue with JS and/or client library though.
And then the problem is confounded by the fact that, ironically, DNS works so well that we don’t think of it as a primary point of failure. So inevitably, when there is a DNS problem, it’s the last thing we check. This just reinforces the idea that the problem is always DNS… because in those long, hard to troubleshoot instances… the problem was DNS.