My data is from a real-world application. One that gets plenty of traffic. Friendly has served almost 50 million hits since we put it in to production two weeks ago.
It actually happens to be quite a write-intensive workload. We have definitely seen a slow down on writes, but the speed up on reads has more than compensated for it.
We do have more data than RAM. But, most of the data that actually gets read is fresh, so it's hot in cache.
Of course Friendly isn't going to be right for everybody. But, I just want to make it clear that my data isn't from synthetic benchmarks. It's from production.
I didn't mean to imply that those benchmarks are synthetic. What I had in mind is that when you write some software, you will improve it to solve your problem better than other software (why would you do it otherwise ;) ). I meant real-world as in -- from various sources and applications -- just so that we can see how useful it is and in what situations it's better / worse.
It actually happens to be quite a write-intensive workload. We have definitely seen a slow down on writes, but the speed up on reads has more than compensated for it.
We do have more data than RAM. But, most of the data that actually gets read is fresh, so it's hot in cache.
Of course Friendly isn't going to be right for everybody. But, I just want to make it clear that my data isn't from synthetic benchmarks. It's from production.