3 ms·
That's approximately 2 hits per second. If you're serving static content (or heavily cached) you could handle that with a Raspberry PI. Heck you could probably
by zrail 12y ago
That's approximately 2 hits per second. If you're serving static content (or heavily cached) you could handle that with a Raspberry PI. Heck you could probably do it with an arduino.
Edit: this depends heavily on your traffic pattern, of course. Super bursty traffic from Reddit, TechCrunch, etc is going to swamp your IO, but CPU will never dominate the equation.
- toomuchtodo 12y agoMight as well serve it from Amazon S3 with Cloudflare in front of it.
- mattmanser 12y agoOf all the things that would be suited to Amazon S3 with Cloudflare, a simple mail client/server that saves email securely for 10 minutes is not one. At all.
- dpcan 12y agoDepends on your users I think. If 50% of that traffic is during a 10 hour window of time each day, that could be around 70 views per second. And pulling email for an account could be more costly than a static page view. Then if he's getting that many views, he could be processing tens or hundreds of emails a day per account more or less.... Could get expensive.
- discardorama 12y ago> If 50% of that traffic is during a 10 hour window of time each day, that could be around 70 views per second. How do you get that? Assuming 4M/month, that works out to 130K/day. Even if all that traffic comes in a 10-hour window, that works out to 130,000/36000 =~ 4/sec, not 70/sec.