>
> show us the output of "ifconfig -a" on each box.
>
Yeah ... did you try to force media opt to 100baseTX full duplex w/
ifconfig ?
I had once a lot of problems connecting 3C905 (XL) cards to 3COM
switches, until i tried to force the negociation ...
To Unsubscribe: send mail to [EMAIL
Thanks for the great help on this. It's hard to find any really good data on tweaking
these kinds of things, to I mess
with things (and go off suggestions from others) until I see benefits, and test from
there. I haven't hit any problems
from them yet, but I'm sure they are on their way.
On
Eric Anderson wrote:
>
> Oh, well, I thought you said "10mb/s", not "10MB/s" .. that makes
> it a bit different. I wonder if it could still be a tcp window
> size or something.. Try these sysctl's on C:
> vfs.nfs.gatherdelay=0
> vfs.nfs.async=1
> vfs.vmiodirenable=1
Alfred stated that he had se
Danny Braniss wrote:
> setup:
> host A: dual pentium III/1GHz (Dell 2450)
> host B: dual pentium III/950MHz (Intel STL2)
> host C: Pentium III/1GHz (Dell GX150)
>
> all connected at 100Mgb full duplex
> all three are running FreeBSD 4.4.
>
> all three have identica
heheh.. well, that definitely could be it.. Let me know what you find out..
Eric
Danny Braniss wrote:
>
> > Oh, well, I thought you said "10mb/s", not "10MB/s" .. that makes it a bit
>different. I wonder if it could still be a tcp window size or something.. Try these
>sysctl's on C:
> ...
> Oh, well, I thought you said "10mb/s", not "10MB/s" .. that makes it a bit
>different. I wonder if it could still be a tcp window size or something.. Try these
>sysctl's on C:
...
i will, but im beginning to believe that it's memory related, not the
quantity (they all have over 256M) but qua
Oh, well, I thought you said "10mb/s", not "10MB/s" .. that makes it a bit different.
I wonder if it could still be a
tcp window size or something.. Try these sysctl's on C:
vfs.nfs.gatherdelay=0
vfs.nfs.async=1
vfs.vmiodirenable=1
kern.ipc.maxsockbuf=2097152
kern.ipc.somaxconn=8192
kern.ipc.max
> And what happens when you go from A or B to C? Have you been running a top or systat
>-vmstat while this is happening?
> I'm thinking it might be a purely IO thing, on the proc box. I have seen similar
>slowness with the default FreeBSD
> install on single proc boxes, but a few sysctl's seem
And what happens when you go from A or B to C? Have you been running a top or systat
-vmstat while this is happening?
I'm thinking it might be a purely IO thing, on the proc box. I have seen similar
slowness with the default FreeBSD
install on single proc boxes, but a few sysctl's seem to do t
> How many times did you run the test? Could it have been cached in host B, but not
>C? What about disk performance?
> Maybe one is ATA66 or 100, and tthe other is not? Host C may only be UDMA33, and
>possibly have a slow drive, with a
> lower amount of memory for caching. Did you rebuild k
How many times did you run the test? Could it have been cached in host B, but not C?
What about disk performance?
Maybe one is ATA66 or 100, and tthe other is not? Host C may only be UDMA33, and
possibly have a slow drive, with a
lower amount of memory for caching. Did you rebuild kernels o
11 matches
Mail list logo
