[OpenAFS] Web Browsers

Wed, 09 Oct 2002 09:59:44 -0500

--------------000505060806080904010103
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>
>
>>Okay, I checked the cache and this is what I had:
>>AFS using 73370 of the cache's available 100000 1K byte blocks.
>>The file was about 4MB so it was larger than the cache. So I increased my
>>    
>>
>
>Eh?  100,000 1K blocks is a 100MB cache  4MB = 4000K == 4000 1K byte blocks
>So your cache was fine..
>
D' oh! Sorry, sometimes I just don't think. Anyway that would explain 
the change
from 73370 to 77294 Roughly 4MB right? 

>>cache by 10x to: 1000000 1K byte blocks. and re-tried the download. I
>>noticed the cache usage did not increase much. AFS using 77294 of the
>>cache's available 1000000 1K byte blocks. Then I noticed network
>>activity continued when the browsers were hung. So I waited several minutes
>>and the download eventually completed. It is strange that during that
>>time I
>>cannot stop the download or the browser without taking aggresive action.
>>Yet it appears after it does finally complete the browser returns to normal.
>>    
>>
>
>Note that AFS uses write-back caching..  It will wire out the data to
>the server at "close()".  How fast is your network link between your
>client and your AFS server?  If it's a slower link (like a Cablemodem)
>then writing out 4MB can take a bit of time.
>  
>
I have 100MB to my desktop that is through a switch to the 100MB subnet the
AFS server is on. We have had performance issues all along. Maybe it is time
for me to dig in and see if I can increase performance at all. I have no 
reason to
believe the issue is the network. I do believe it has something to do 
with the
AFS servers themselves.

Do you have any suggestions on how to do that?

--Mike

--------------000505060806080904010103
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
<blockquote type="cite" cite="midsjm8z17zn5y.fsf@kikki.mit.edu">
  <blockquote type="cite">
    <pre wrap="">Okay, I checked the cache and this is what I had:
AFS using 73370 of the cache's available 100000 1K byte blocks.
The file was about 4MB so it was larger than the cache. So I increased my
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Eh?  100,000 1K blocks is a 100MB cache  4MB = 4000K == 4000 1K byte blocks
So your cache was fine..</pre>
</blockquote>
D' oh! Sorry, sometimes I just don't think. Anyway that would explain the
change <br>
from 73370 to 77294 Roughly 4MB right?&nbsp;
<blockquote type="cite" cite="midsjm8z17zn5y.fsf@kikki.mit.edu">
  <blockquote type="cite">
    <pre wrap="">cache by 10x to: 1000000 1K byte blocks. and re-tried the download. I
noticed the cache usage did not increase much. AFS using 77294 of the
cache's available 1000000 1K byte blocks. Then I noticed network
activity continued when the browsers were hung. So I waited several minutes
and the download eventually completed. It is strange that during that
time I
cannot stop the download or the browser without taking aggresive action.
Yet it appears after it does finally complete the browser returns to normal.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Note that AFS uses write-back caching..  It will wire out the data to
the server at "close()".  How fast is your network link between your
client and your AFS server?  If it's a slower link (like a Cablemodem)
then writing out 4MB can take a bit of time.
  </pre>
</blockquote>
I have 100MB to my desktop that is through a switch to the 100MB subnet the
<br>
AFS server is on. We have had performance issues all along. Maybe it is time<br>
for me to dig in and see if I can increase performance at all. I have no
reason to <br>
believe the issue is the network. I do believe it has something to do with
the <br>
AFS servers themselves.<br>
<br>
Do you have any suggestions on how to do that?<br>
<br>
--Mike
</body>
</html>

--------------000505060806080904010103--