I have a 3Com 10/100 switch, it's not too expensive but I wouldn't
classify it as cheap... But that has never been the problem as I can
acheive good rates between Windows machines (I have XP on a laptop and
2000 on a desktop). My probem is specifically SAMBA 3 running on FC3 on
a ProLaint 2500... Next time I'm at home (probably this weekend) I'll
try setting up a server on the laptop (P4 3.4G w/ HT, 1 GB of RAM, 1
Gbps BroadCom NIC - hardware is flawless) which has FC3 dual boot. But I
have a feeling that the results wont be that different, if they are I'll
settle for a new DMA capable NIC on the ProLiant... But since I've
compiled Samba 2.2.12 I may as well try it and see if I can get better
performance. In anycase I'll let you know.
Peter.
AragonX escreveu:
<quote who="pb">
When trying to improve upon the 7 Mbyte/sec I found that nothing helped
at all. Compiling with different flags (O3, etc), made no difference
(cpu load very low anyway) Kernel made no difference (I used Slakware's
v.8, v.9 and currently use v.10) With or without Hyperthreading on the
P4 enabled (via custom kernels) made no difference.Different 100TX patch
cables made no difference.
It was the crap switch in my case.
Following the advice from you and others, I tried a new switch. The time
to open the application went down from 3 minutes to about 1.5 minutes.
This is a great improvement but I fear it treated the symptom and not the
problem. A minute and a half to open an application is still far too
long. The amount of data going over the network is huge. The network
light flashes constant for the entire 1.5 minutes. Next I'll try a
network sniffer and see what is being transmitted.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba