insightful's comments

I've run a sporadically popular (100s of thousands of uniques on some days) blog on Wordpress for years. All running on a single spot instance (if it was killed I have a script to roll over in minutes).

The database, Wordpress, the file storage. Entirely self contained.

I occasionally persist the AMI so I can spin up a new updated system base, and have regular backups of the files and database. My monthly cost is ~$9 on AWS. I've had literally minutes of downtime over the past several years.

Obviously this guide is geared to a more serious installation, but there is the danger that the more reliable a system becomes, often the less reliable it becomes. EFS and NLB configuration changes or problems taking the system offline, for instance.

These tests churn GBs of data (necessary given how fast flash is), rendering the cache largely irrelevant. As I mentioned elsewhere, it is incredibly unlikely that parallelism plays a part (and has never been the case in prior devices, nor is it the case with the vast majority of SSDs. Anyone blindly buying larger for more parallelism is very likely to be disappointed). Different vendors make their memory solutions, and there are huge variations in options. We've seen this across a single model of a set size when two different vendors provide the storage.

In the end it really won't make a difference for real world use.