Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The story: Hi guys. I'm among the people responsible for serving the results of the most anticipated (by number of people participating) annual entrance exam in my state. As such, when our results are published, the interest is overwhelming. In the past we delegated the responsibility of serving the results to the media, but that spoils a little the officialness of these results.

This year we went with a little (long overdue) experiment of using lighttpd instead of Apache as well as other physical network optimizations I wasn't directly involved with. The results were very satisfactory. The server didn't choke even once, nor we saw any of the usual Twitter complaints on unavailability and/or slowness that were previously common. However, because we still delegated the first publication of the results to the media I'm still not 100% sure we can handle the load of actually publishing the results first.

The question: Now because these files are like 14MB in total and a true lightweight Linux distribution isn't that big either, I'm thinking: what if next year we run full RAMdrive? Is there any? Is that useful? Is that worth it for a team that uses Debian almost exclusively?

Are there other optimizations that I should be focusing on instead?

share|improve this question

closed as not constructive by Chris S Sep 21 '12 at 15:49

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Shopping Questions are Off-Topic on any of the Stack Exchange sites. See Q&A is hard, lets go Shopping and the FAQ for more details. That said, RAMdrives probably aren't going to make any noticeable difference. A properly configured Apache, reasonable server hardware , and 14MBs of static file(s) should be able to blast a 100Mb connection, and 1Gb+ shouldn't be too hard either. Also, this is the poster case for "cloud" architecture; AWS, several EC2 VMs, ELB to load balance... Or if it's all public data, a CDN. –  Chris S Sep 21 '12 at 15:49
Unless you've got a wealth of connectivity - I can't imagine the web server software being the bottleneck. At 14MB for a file, it will only take 8 downloads to saturate a 100Mb connection. Just use a CDN - that's the right tool for the job. –  Ben Lessani - Sonassi Sep 21 '12 at 15:49
Perhaps @sonassi means eight simultaneous downloads. I do agree that a CDN is the right tool for this. –  Michael Hampton Sep 21 '12 at 15:52
Yes, simultaneous. The answer was closed when I was mid-sentence, so I gave up bothering to write it :( –  Ben Lessani - Sonassi Sep 21 '12 at 16:07
Well, fancy that. As far as I care, the question was answered satisfactorily by everyone including the one who bothered to close answers for it. Thanks guys. –  Ekevoo Sep 21 '12 at 17:57