How to size hardware for Reverse-Proxy

We are implementing an online store and would like to setup a Reverse-Proxy to allow access.  This server will handle SSL as well.  How do I size the hardware needed for this.  I do not have a hit count to provide.
Please provide the method commonly used.
Who is Participating?
a1jConnect With a Mentor Commented:
It all depends on amount of content your serve and amount of traffic.
If you use squid and many small files (hundred thousands) your best choice will be squid COSS storage. It will be about 10-50 times faster than default storage because it works around filesystem limitations
If number of files is small you can use default storage because you will benefit from fs cache.

Squid alone can easily do 10k requests per second. But SSL will be costly.
Keep in mind that squid2 does not support SSL and squid3 considered to be in beta stage still.

If you dont need cache then you can just use apache proxy (or nginx or anything else - it is matter of personal preference). APache proxy itself without SSL will do 10k requests/sec easily with no CPU load. I dont know about SSL though, never tried to push big traffic through it. It is all will be as fast as openssl library can be with any type of webserver.
Yeh those numbers are for generic XEON medium-grade server. 4 gigs, quad core and so on.
Starrett2005Author Commented:
We will be using Apache Reverse-Proxy.
We do not know how many requests we will have.  This is the first implementation of an online store.
A wild guess, please size for 30 con-current SSL requests.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.