Again,
H'mmm
Have you check your cache hit ratio before expanding it.
The AFS cache is a software cache with no hardware assist, like
associative addressing, this would find any data in one access cycle,
no matter how big.
What you see on such a SW cache which is far too large, that the sw
spends loads of time scanning through the cache al in order to find
that the stuff isn't there.
I have seen this in practice on a Oracle cache. The best is to tune you
cache lower for 95% hit rate iso larger in an attempt to get 100%.
Joop
----------
| From: dwinkel / mime, , , [EMAIL PROTECTED]
| To: micbeddi / mime, , , [EMAIL PROTECTED]
| Cc: briansp / mime, , , [EMAIL PROTECTED]; info-afs / mime, , ,
[EMAIL PROTECTED]
| Subject: Re: AFS/HTTP Server Performance
| Date: Thursday, September 19, 1996 6:46AM
|
| > Brian,
| >
| > I can't write much right now, but we are running our http server on AFS
| > with no problems. I am running on a Sun SPARC 5 with a 2GB cache under
| > Solaris 2.5 and AFS 3.4. Again, no problems at this time...Mic
|
| Hmmm... You might want to check AFS performance. My servers run a LOT
| faster with a 180MB cache, than when the cache was 1GB. All those drive
| seeks. (That's another bottleneck, my AFS cache drive is up to 50%+ busy
| according to iostat, so I'm looking for faster drives, or information on
| how well striping the AFS cache works under a heavy load. It's currently
| on a 1 GB Quantum Fireball.)
|
| ~~~~
| [EMAIL PROTECTED] f u cn rd ths, u cn gt
| UofM/ITD Expert Consultant/Web Admin Team a gd jb n cmptr prgmmng
| 535 W. William, Ann Arbor, MI 48103
|
