Netapp's NFS performance is faster, primarily because of the huge gobs of
NVRAM that their boxes have. This is especially true when the client(s)
write to disk. When the write request is sent to the NetApp, the NetApp
immediately replies with a 'write is complete' instead of waiting for it to
write to disk. (The reason it can get away with this is because of the
NVRAM). Also, I would imagine the NetApp is highly optimized to cache data
for read performance as well as write performance...
Of course, NetApps cost a LOT of $. Well, maybe there's a few on EBAY or
something..
> -----Original Message-----
> From: Dana Quinn [mailto:dana@xxxxxxxxxxxx]
> Sent: Saturday, April 28, 2001 7:52 AM
> To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: nfs mounted web dierstories?
>
> <Nod> We have a similar setup, using a Netapp. We're serving 8-10
> million pageviews/day with this setup, and iostat times for file
> access on the realservers is lower with the Netapp than it was
> with local disk. Of course you have a nasty single point of
> failure there... so we use rdist or rsync to make local disk
> backup copies.
>
> Netapp claims that their NFS implementation is faster than most,
> so using some out of the box OS vendor's NFS implementation might
> not perform as well. Of course, that could be marketing drivel
> from Netapp.
>
> Overall, to address the original question - rather than complicating
> your setup, you might benefit from formalizing your
> developer's process of making content go live - provide them a
> push tool that wraps around rsync or rdist. Of course developers
> usually hate losing access to ftping content right to the
> servers... so have fun with that! :)
>
> dana
>
> --
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> I'm a fool - and she let me prove it + Dana Quinn
> -Cesar Rosas "Little Heaven" + dana@xxxxxxxxxxxx
> + linux type guy
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|