Re: domain vs. TCP/IP sockets & load balancing

On a sidenote, you can get FireWire adapters that support Linux for $45 each (do a search for "firewire adapter" on pricewatch.com), and there is software to treat these as ethernet interfaces (http://www.chez.com/kayle/ieee_1394.htm). The are 400Mbs, and have very low latency. It would work great if you had a dedicated database server that you wanted tied into your servers, but not hooked into the internet directly. Create a separate network with FireWire, with a route that goes only to your database server. Should be very fast, and very cheap. I haven't had time to do it, so if someone does it, let me know how it works. Brian > Domain sockets are always faster, there is no network layer to go > through. > > I work at a site where we currently have ~1.5 million registered > users. Our database is a separate machine and all of our web servers > query is over the 100Mbit wire (TCP sockets). We are in the middle of > a network upgrade, where our network backplane will be able to do GigE > and not just 100MB. This is a natural evolution. > > We are one of the biggest PHP/MySQL sites around, so, if you are just > starting out, I wouldn't worry about network traffic at all if you are > doing 100Mbit to your database server. You'll surely run into other > issues before you saturate your network. > > -jeremy brand > _______________________________________________________________________ > GnuPG Fingerprint: 9F5E 95E0 1CC2 E054 84EA 6099 8ACD 9DBA D2C0 5EA9 > _ http://www.JeremyBrand.com/Jeremy/Brand/Jeremy_Brand.html for > more __ > > On Sun, 8 Oct 2000, Frank Joerdens wrote: > > > Date: Sun, 8 Oct 2000 23:57:47 +0200 > > From: Frank Joerdens <frank@joerdens.de> > > To: php-general@lists.php.net > > Subject: [PHP] domain vs. TCP/IP sockets & load balancing > > > > I seem to recall that a while back the received wisdom was that > > communication with a database was _significantly_ faster over domain > > sockets than over TCP/IP sockets, so that a load balancing scheme based > > on putting the SQL server and the webserver on different hosts was > > likely to be futile, even if there was sufficient bandwidth (e.g. 100 > > MBit Ethernet) between the two hosts. Is this database specific? Is it > > nonsense? What do you do if you want load balancing with an SQL server > > in the middle? Does anyone have any pointers to further information > > about this question? > > > > Cheers Frank > > > > -- > > frank joerdens > > > > joerdens new media > > urbanstr. 116 > > 10967 berlin > > germany > > > > e: frank@joerdens.de > > t: +49 (0)30 69597650 > > f: +49 (0)30 7864046 > > h: http://www.joerdens.de > > > > pgp public key: > > http://www.joerdens.de/pgp/frank_joerdens.asc > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > > For additional commands, e-mail: php-general-help@lists.php.net > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net