Vijayendra's questions

I want to set up Nginx as my web server. I want to have image files cached in the memory (RAM) rather than disk. I am serving a small page and want a few images always served from RAM. I don't wish to use Varnish (or any other such tools) for this as I believe Nginx has a capability to cache contents into RAM. I am not sure as to how I can configure Nginx for this? I did try a few combinations but they didn't work. Nginx uses disk all the time to get the images.

For example, when I tried Apache benchmark to test with following command:

ab -c 500 -n 1000 http://localhost/banner.jpg

I get the following error:

socket: Too many open files (24)

I guess this means Nginx is trying to open too many files simultaneously from the disk and OS is not allowing this operation. Can anyone please suggest me a correct configuration?

What I am asking is a very common question that comes to any developer's mind when he/she wants to host a server but a precise answer is not easily available. I need to host a server which returns HTTP response of 20KB. This server is expected to get ten million request a day, maximum 10 thousand request per minute. What server capacity (RAM, bandwidth etc) I should have? Lets safely ignore other factors like storage, database capacity like SQL etc. The prime objective of this question is to judge hardware estimation in terms of bandwidth and RAM(or other hardwares) that can handle so many simultaneous connections.

It would be very helpful not just to me but to anyone interested, if the person answering this question provide explanation about the factors that were considered to arrive at the answer. The formula governing these factors will help anyone to change requirements in my original question and arrive at the answer needed.