Unlink vs. DEL – A deep dive into how it works internally in Redis
1–10 of 18 posts
Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#2Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#3Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#4[flagged]
Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#5[flagged]
Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#6[flagged]
Terms like this one, “alignment”, “low hanging fruit”, all not super accurate but established industry terms.
Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#7[flagged]
From an explanation analogy perspective people typically say something like “we’re just going to touch the surface”.
Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#8[flagged]
> A couple of my internet stranger friends and chatGPT says this number was chosen by redis developers post a massive benchmarking. The consideration was trade-off such as performance vs blocking, memory management and avoiding overhead.
Deep dive is a colloquialism in english, at least in the US.
We are going to see a lot of these about Redis since the source has so many comments. Basically re-stealing Salvatore's work again, unpriced asset.
Re: Unlink vs. DEL – A deep dive into how it works internally in Redis
#9[flagged]
"deep dive" has been around for quite some time https://trends.google.com/trends/explore?cat=5&date=all&q=%2...