home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.admin
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!sun-barr!ames!saimiri.primate.wisc.edu!relay!relay2!afterlife!svfenge
- From: svfenge@afterlife.ncsc.mil (Steven Fenger)
- Subject: Re: what is prestoserve??
- Message-ID: <1992Nov5.030447.12625@afterlife.ncsc.mil>
- Organization: The Great Beyond
- References: <1992Nov3.042210.22311@afterlife.ncsc.mil> <1992Nov4.212349.19891@sj.ate.slb.com>
- Date: Thu, 5 Nov 1992 03:04:47 GMT
- Lines: 21
-
- In article <1992Nov4.212349.19891@sj.ate.slb.com> poffen@sj.ate.slb.com (Russ Poffenberger) writes:
- >I am not sure at what level the write caching is done in the PrestoServe, but
- >in an Auspex file server, their SPIII option which has a similar battery
- >backed write cache feature, even if your NFS write mix is not high, the write
- >cache can have a dramatic impact on total throughput. In the Auspex, the write
- >cache is done at a very low level, caching ALL disk writes. Even though my
- >average NFS write mix is around 5%, my actual disk write percentage is closer
- >to 30 or 40%.
-
- The Presto also caches all disk writes. The thing is that the Presto
- board seems to always be pushed as an enhancement to NFS, even though
- it really has nothing to do with NFS. So in order to justify a Presto
- board for an increase in NFS performance, NFS writes need to be 10%
- or greater of your NFS load.
-
- I'm surprised that Sun hasn't also started pushing the Presto board as
- a database excellerator, since it would also speed up a database if that
- database required a lot of updates.
- --
- Steven Fenger fenger@cps.msu.edu svfenge@afterlife.ncsc.mil
- What for you bury me in the cold, cold ground?
-