really random question - but what is used to create the images in this blog post? I see this style quite often but never been able to track down what is used.
[deleted]
Analyzing the codebase of Caffeine, a high performance caching library
11–20 of 56 posts
Re: Analyzing the codebase of Caffeine, a high performance caching library
#12It would be interesting to see this on reddit's workload. The entire system was designed around the cache getting a 95%+ hit rate, because basically anything on front page of the top 1000 subreddits will get the overwhelming majority of traffic, so the cache is mostly filled with that.
In other words, this solves the problem of "one hit wonders" getting out of the cache quickly, but that basically already happened with the reddit workload.
The exception to that was Google, which would scrape old pages, and which is why we shunted them to their own infrastructure and didn't cache their requests. Maybe with this algo, we wouldn't have had to do that.
Re: Analyzing the codebase of Caffeine, a high performance caching library
#13Interesting deep dive on the internals of Caffeine, a widely used JVM caching library.
[flagged]
Re: Analyzing the codebase of Caffeine, a high performance caching library
#14Caffeine is a gem. Does what it claims, no drama, no scope creep, just works. I've used it in anger multiple times, most notably in Apache Cassandra and DataStax Astra, where it handles massive workloads invisibly, just like you'd want.
Shoutout to author Ben Manes if he sees this -- thanks for the great work!
Re: Analyzing the codebase of Caffeine, a high performance caching library
#15really random question - but what is used to create the images in this blog post? I see this style quite often but never been able to track down what is used.
https://excalidraw.com/
For something a bit lower level, try:
It's what powers the sketch-like look from many of the sites above.
Re: Analyzing the codebase of Caffeine, a high performance caching library
#16It would be interesting to see this on reddit's workload. The entire system was designed around the cache getting a 95%+ hit rate, because basically anything on front page of the top 1000 subreddits will get the overwhelming majority of traffic, so the cache is mostly filled with that. In other words, this solves the problem of "one hit wonders" getting out of the cache quickly, but that basically already happened wi…
Wouldn’t one hit wonders still be an issue? They might get evicted relatively fast anyway but assuming an LRU each will still take a cache entry until they go through the entire thing and finally get evicted.
Although if that’s your concern you can probably just add a smaller admission cache in front of the main cache, possibly with a promotion memory.
Re: Analyzing the codebase of Caffeine, a high performance caching library
#17It would be interesting to see this on reddit's workload. The entire system was designed around the cache getting a 95%+ hit rate, because basically anything on front page of the top 1000 subreddits will get the overwhelming majority of traffic, so the cache is mostly filled with that. In other words, this solves the problem of "one hit wonders" getting out of the cache quickly, but that basically already happened wi…
what are/were Reddit's top two or three cached structures / things?
guessing post bodies and link previews feels too easy.
comment threads? post listings?
was there a lot of nesting?
it sounds like you're describing a whole post--use message, comments, and all--for presentation to a browser or crawler.
(sorry, saw the handle and have so many questions :D)
Re: Analyzing the codebase of Caffeine, a high performance caching library
#18Codebase has >16k stars on GitHub and only 1 open issue, and 3 open PRs. Never seen that before on a highly used codebase. Kudos to the maintainer(s).
Re: Analyzing the codebase of Caffeine, a high performance caching library
#19Caffeine is a gem. Does what it claims, no drama, no scope creep, just works. I've used it in anger multiple times, most notably in Apache Cassandra and DataStax Astra, where it handles massive workloads invisibly, just like you'd want. Shoutout to author Ben Manes if he sees this -- thanks for the great work!
Plus Ben made it extremely easy to migrate from Google Guava’s cache. It’s mostly the same API and way more performant to switch to Caffeine.
Re: Analyzing the codebase of Caffeine, a high performance caching library
#20Codebase has >16k stars on GitHub and only 1 open issue, and 3 open PRs. Never seen that before on a highly used codebase. Kudos to the maintainer(s).
I went through some of the issues to see how aggressively they close them and found this gem: https://github.com/ben-manes/caffeine/issues/1824#issuecomme...