Wow, thanks for running the additional tests Roy, the numbers look great! You’re definitely right about different URLs vs hammering the same URL, and it definitely shows on larger sites with a huge amount of posts.

I appreciate your testing and feedback!

Had some time today after all, so I updated the post with some hey benchmarks.

I’ll see about changing the NGINX cahe folder location. Since this is my live site, I’m hesitant to mess with the config.

I don’t really have the setup (or the time) to run proper comparitive tests, but I’m pretty sure someone will do some proper benchmarking.

I mean tmpfs versus a regular ext4 for Nginx fastcgi_cache, see if that affects the actual requests per second with something like ab or hey.

What kind of benchmarks would you have in mind? I did my tests with this setup.

I guess with tmpfs being RAM + disk swap, SSDs having DRAM caches and OSs caching stuff there’s really no telling where exactly data is from.

What the benchmarks do seem to indicate is that it’s all very fast.

If Surge would provide microcache-like levels of performance on systems where microcache isn’t available (such as shared hosting), that alone would make it a valuable tool.

Ah, interesting! I don’t think there’s any added benefit to forcing the OS to keep your cache files in memory (physical or swap) with tmpfs, versus letting the kernel take care of paging data in and out as necessary (I read this as free LRU). I’d be curious to see some fresh benchmarks though! 🙂