Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [wp-hackers] Forum post: Huge server hits

  • To: wp-hackers@xxxxxxxxxxxxxxxxxxxx
  • Subject: Re: [wp-hackers] Forum post: Huge server hits
  • From: Roy Schestowitz <r@xxxxxxxxxxxxxxx>
  • Date: Wed, 13 Jul 2005 07:46:20 +0100
  • Delivery-date: Wed, 13 Jul 2005 07:46:25 +0100
  • Envelope-to: r@schestowitz.com
  • In-reply-to: <42D4B35D.2000100@mullenweg.com>
  • References: <003701c58708$08bded00$6702a8c0@DB><42D401DE.2030800@tamba2.org.uk> <42D42072.5060202@tamba2.org.uk> <022801c58726$d88a0c80$6e01a8c0@sixfour> <42D46E99.4090708@midnightcircus.com> <42D4B35D.2000100@mullenweg.com>
  • User-agent: Internet Messaging Program (IMP) H3 (4.0)
Quoting Matthew Mullenweg <m@xxxxxxxxxxxxx>:

Owen Winkler wrote:
I took large segments of your post, reworded some things, added a bunch, and posted it here:

http://codex.wordpress.org/User:Ringmaster/WordPress_in_High_Traffic

Everyone please edit and extend.

I think it makes sense to put things in order of practicality. It's much easier to use gzip or install a caching plugin than changing your network interface or bandwidth peering arrangements. I *seriously* doubt that anyone who has asked about this in the forums was running into network card limitations.

Peering arrangements are a good idea, but compression will not deal with increase that scales by orders of magnitude. Network card limitations are very hard to meet. Many dedicated server come with dual Gigabit Ethernet cores. Even Slashdot cannot beat that in terms of bandwidth unless Tiger for Intel architecture is up for grabs. If Slashdotted sites go doolaly, you can always use the Network Mirror provided that you don't need very much browsing depth.

http://www.networkmirror.com/

Roy

--
Roy S. Schestowitz
http://Schestowitz.com


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index