× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



As a side note, there's the issue of caching.  If you're talking about HTTP
304 responses (cached) as opposed to HTTP 200 (found and sent) responses,
then your hit total might be much, much higher.  But for those situations,
the load is negligible on the machine, and I suspect any HTTP server could
handle thousands of those requests a second.

Joe

> -----Original Message-----
> From: Joe Pluta
>
> I find this difficult to believe.  3200 per second?  What size is your
> response?  Let's say it's trivial, only 1KB - that's 25MBit/sec, more than
> 10 times T1 speed.  You have that kind of pipeline to the
> Internet?  And if
> your response is anything like a normal page, say 5KB without graphics,
> you're talking over 100MBit/sec, or more than double a dedicated T3
> connection.  You have perhaps multiple T3 lines?  With graphics it quickly
> escalates, of course, to T4 and above.
>
> I think you might want to review your numbers one more time.
>
> Joe
>
> P.S. The first page I clicked to on Seta Corporation was 14KB without
> graphics.  The graphics were another 40KB.  I don't know how
> large the Flash
> amimation was, but even at a paltry 50KB total, to support 3200 hits a
> second, we're talking well over 1GBit/sec, or 25 dedicated T3 lines, or 4
> dedicated T4 lines, or roughly twice the bandwidth of the TAT-9
> transatlantic fiberoptic cable.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.