Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are running 3 PHP web servers with the web directory (including the php files to be ran locally) pulled from a their own local SSD drive. We are deciding wheter to install a SAN to server our web directory from. The main reason for the switch to the SAN is to keep the files in sync and because the SAN is much more stable.

Does anyone have experience with the latency and throughput of a SAN vs a local SSD? Or what kind of performance loss/gain we will get.

share|improve this question
People are going to need a lot more information to answer your question. A SAN can be much faster than a single local SSD but it really depends on the SAN and it's disk configurations, interconnect, etc. What sort of SAN you can get is going to depend on your budget. – 3dinfluence Nov 24 '10 at 20:55
up vote 3 down vote accepted

Unless your web-server is much busier or larger than is typical, the performance difference shouldn't be significant. The few areas where an SSD may outperform is if you're serving tens to hundreds of millions of files through the web and they're all on the same file-system. In that case the low latency of an SSD will shine through.

In the more typical "tens to hundreds of thousands" serving case the increased latency of the SAN should be markedly less than the latency already incurred by serving over the WAN. If you are concerned about latency, make sure your SAN contains lots of spindles instead of lots of space.

share|improve this answer
Right on. Wonder if he's running a database in behind that is on the SAN? that might make a difference. – Matt Nov 24 '10 at 23:43

You're not clear but I think you've got the SSD in one server, sharing it to the others via some form of network share - is that right?

If that's the case then unless it's one hell of a SAN the SSD will be significantly faster in terms of both latency and throughput for the server that contains the SSD. The other machines getting at this data over the network will be limited by that network link and the sharing capabilities of the machine with the SSD - even with the fastest network setup this will be much slower than the SSD and is likely to be much slower than a SAN.

So if my assumption about your usage is right then you'll have one very quick server and two much slower servers (if they do perform a lot of disk work anyway, it's irrelevant if not).

If you do a lot of disk work and want consistent performance then moving to a SAN will help with that, no single server is likely to have quicker disk access than another - and it's likely to be perfectly adequate for most needs too.

share|improve this answer
Update: Each server has their own SSD – Willemk Nov 24 '10 at 21:06
Thanks for clarifying. The SSD will be faster but what do you mean by "the SAN is much more stable", what stability issues have you had with SSDs? – Chopper3 Nov 24 '10 at 21:11
We've had an SSD (server has a single drive) crash in each server about once every 8 months. – Willemk Nov 24 '10 at 21:15
Try EFDs, not consumer SSDs. – Chris S Nov 24 '10 at 21:21
Oh dude, you won't miss the speed of those SSDs at all. – Chopper3 Nov 24 '10 at 22:04

SSD might help with log files on a very busy system. but is probably a bad use of resources.

Depending on the size and access distribution of your web site, you may find that most of the data is served from buffer cache in memory. In this case disk access statistics are relatively insignificant.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.