The short answer is no.
The somewhat longer answer follows now. I’ve run benchmarks with three scenarios:
- Plain WordPress
- WordPress running on a tmpfs ramdisk
- WordPress running with WP-FFPC (with nginx interfacing directly with a memcache backend)
I have run the benchmarks with siege and the following settings:
siege -b -t60s <target url> which boils down to roughly 15 concurrent users per second in 60 seconds.
Outcome of scenario 1: 285 hits in 60 seconds
Outcome of scenario 2: 296 hits in 60 seconds
Outcome of scenario 3: 14.117 hits in 60 seconds
So don’t bother with tmpfs for running WordPress and put your memory in to a WordPress caching solution.