Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!m.cs.uiuc.edu!carroll
From: carroll@m.cs.uiuc.edu
Newsgroups: comp.unix.i386
Subject: Re: Tuning Streams
Message-ID: <70400003@m.cs.uiuc.edu>
Date: 18 Mar 90 01:36:45 GMT
References: <4Y62V32xds13@ficc.uu.net>
Lines: 44
Nf-ID: #R:<4Y62V32xds13@ficc.uu.net>:-26:m.cs.uiuc.edu:70400003:000:2599
Nf-From: m.cs.uiuc.edu!carroll    Mar 17 17:03:00 1990


/* Written  6:32 pm  Mar 14, 1990 by dbrown@apple.com in m.cs.uiuc.edu:comp.unix.i386 */
In article <4Y62V32xds13@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>> We're experiencing some problems with a network implementation on an intel
>> 320 running System V/386. The performance is dog slow,  [ ... ]

>One easy thing to do is run "crash" and type "strstat" to get streams 
>statistics, and look for failures and/or maximums near the limits [ ... ]
/* End of text from m.cs.uiuc.edu:comp.unix.i386 */

I'm having very slow response from the network, under 386/ix 2.0.2. My stats
from crash look like
ITEM                  CONFIG   ALLOC    FREE         TOTAL     MAX    FAIL
streams                   96       48      48            81      51       0
queues                   300      238      62           216     252       0
message blocks          2150      106    2044        266571     139       0
data block totals       1720      106    1614        238030     139       0
data block size    4     256        0     256         17618       3       0
data block size   16     256       14     242         26723      19       0
data block size   64     256        8     248        152742      39       0
data block size  128     512       84     428         15986      91       0
data block size  256     128        0     128         24795       3       0
data block size  512     128        0     128            27       2       0
data block size 1024      64        0      64            42       1       0
data block size 2048      64        0      64            97       4       0
data block size 4096      56        0      56             0       0       0

Count of scheduled queues:   0

Additionally, the problem often manifests itself under NFS, when trying to read
files. If the file is longer than a certain (small, roughly a few K), nothing
will be read, while small files will be read just fine. I will get a
"NFS server not responding", while telnet/rlogin/ping all report everything is
fine.
P.S. I looked through old notes, but I didn't see anything on this topic. I
though I remembered such a discussion a while back - if anyone has it, please
email it to me. Thanks.

Alan M. Carroll                "Like the north wind whistling down the sky,
carroll@cs.uiuc.edu             I've got a song, I've got a song.
Conversation Builder:           I carry it with me and I sing it loud
+ Tomorrow's Tools Today +      If it gets me nowhere, I'll go there proud"
Epoch Development Team          
CS Grad / U of Ill @ Urbana    ...{ucbvax,pur-ee,convex}!cs.uiuc.edu!carroll