RE: [PHP] high availability

We're getting a bit off-topic here, but some might find this useful. We, too, use a single NFS share for our servers' root. Our performance is very good. If you use a very fast NFS server, it's possible to get throughput that exceeds that of an average-speed local disk. We use a Network Appliance F720, and the communications happen over a 100Mbps switch that only moves the NFS traffic (i.e. each Web server has two NICs -- one for NFS and one for HTTP/other traffic). Of course, throughput to each Web server will go down as you add more servers to the mix. We find that the convenience of management far outweighs any performance decrease (which I have not been able to detect). Jason Priebe WRAL OnLine http://www.wral-tv.com/ > -----Original Message----- > From: Michael Kimsal [mailto:michael@tapinternet.com] > Sent: Tuesday, November 07, 2000 4:52 p.m. > To: jeremy brand > Cc: alex; php-general@lists.php.net > Subject: Re: [PHP] high availability > > > Jeremy - can you comment as to the performance compared to having > the doc roots on the individual machine drives? > > jeremy brand wrote: > > > We mount our web farms' docroot as an NFS share. AFAIK, this is > > pretty common. > > > > Our performance is excellent. > > > > -jeremy brand > > > > http://www.JeremyBrand.com/Jeremy/Brand/Jeremy_Brand.html for more > > > --------------------------------------------------------------------- > > We cannot do everything at once, but we can do something at once. > > -- Calvin Coolidge > > > > On Tue, 7 Nov 2000, alex wrote: > > > > > Date: Tue, 7 Nov 2000 18:52:32 -0300 > > > From: alex <alex@quad.com.ar> > > > To: michael@tapinternet.com > > > Cc: php-general@lists.php.net > > > Subject: Re: [PHP] high availability > > > > > > > I'd suggest putting things in a database. Not used > coda directly, > > > > but we tried a similar approach under NT writing info > to shared drives, > > > > and the performance wasn't as good as sharing info in a db. > > > > CODA may be vastly different, but SQL makes more sense, imo. > > > > > > Looks like I made a little confusion about this. I was > thinking on using > > > CODA for 2 purposes: > > > 1. store ALL the php scripts (since all web servers will > have to use the > > > same copy of them) > > > 2. store php data (like php sessions) > > > > > > I understand that the php data can actually be stored on > SQL and might be > > > better as you mention, but any idea how reliable will be > to use CODA for > > > storing the php scripts itself ? (so I dont have to rsync > all servers and to > > > avoid having a master/slave relationship between them) > > > > > > > How large of a system do you anticipate this being? > > > > > > I actually don't know for sure. but what I do know is > that we need something > > > scalable in case of success =) > > > > > > Thanks for your comments. > > > > > > Alex Verstraeten > > > Buenos Aires, > > > Argentina > > > > > > > > > -- > > > 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 > > -- > ========================== > Michael Kimsal > http://www.tapinternet.com > 734-480-9961 > > > > -- > 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 >