Very slow performance SAMBA with FC3

[deuch]

A another problem with FC3 ...

Very very low performance with samba, about 300Ko/s with a 100mb network between 2 computers ...

Any idea ?

thanks,
deuch

[deuch]

I hava tried to disable the rules in SElinux for smb, but it still very slow ... I've shut down some services not very useful for me, and no changes ...

The problem is with Nautilus ..? i didn't make a benchmark with a direct smbmount ... i will try this afternoon ...


thx,

deuch

[gushy]

did you ever resolve this issue? It's bugging the hell out of me.

[yoonix]

I'm having a similar issue - my FC3 brand-new install is VERY SLOW. I have samba 3.0.10.fc3.x86_64 and kernel 2.6.9-1.681_FC3.

I have a Athlon 64, SATA RAID-5 6x200GB, which achieves 115MB/second with hdparm, and an all gigabit network. However, Samba read/writes from my windows box (also a high performance machine) are slow as molasses.

Has anyone found a resolution for this problem?

[deuch]

I'm using CIFS instead of Samba ...
It provides "better" performance !! (~ 3-5MB/s on a 100Mb Ethernet Network but there are 2 laptop, with FTP connection, speed is near 10MB/s ... )

Hope it helps,

deuch

[SticknClutch]

I am having similar problems.
My Linux PC is a fresh install of FC3 running on a A64 with one 250GB 7200rpm sata drive. Connected to a Jumbo Frame capable switch through an intel Gigabit nic. Both FC and my windows box are jumbo enabled. I set the MTU's to 9000. I get about 300KBytes transfer rate between both.

Alternativley I get about 8000KBytes per second between my powerbook and my windows PC. The powerbook only has a 100mb nic and I get much higher preformance.

The throughput tests between the windows machine and the FC box where done with vsftpd.

[Void Main]

Are all network operations slow? Have you checked to make sure your duplex settings match between the NIC and the switch? If there is a mismatch things with be extremely slow. I run across this all the time. To see what your interface is running do:

# /sbin/ethtool eth0

If your switch is set to 100mbps/full duplex and the above command shows your interface is at half you can force it to 100 full by:

# /sbin/ethtool -s eth0 speed 100 duplex full autoneg off

Of course you would replace "eth0" with whatever interface you are working on. To make this happen on boot you would add this line to your "/etc/sysconfig/network-scripts/ifcfg-eth0" file:

ETHTOOL_OPTS="speed 100 duplex full autoneg off"

Of course this may not be your problem but it's certainly possible.

[jhawkinsvalrico]

I'm glad that I ran across this thread as I thought that this problem was unique to me. I have a small network (mixed linux and windows environment) and tied everything together using samba. For typical day to day tasks the network works fine. However, I use a windows box that houses two 250 gb disks as a backup system. When I first set this up, I used Nautilus to copy files from my FC3 workstation to the backup system. It was terriibly slow. This is a full duplex 100 mbps network and it was taking forever to copy 6 GB of data to the server. I didn't do this as a test and didn't collect any timings, but I was the only user on the network and I just knew that something was wrong. I decided to try pulling the files off of the FC3 system from the Windows system and it was considerably faster. Just guessing, I'd say at least twice as fast. The bottom line is that whenever I need to copy large volumes of data from one of my FC3 systems to a windows system, I pull the data from the windows system. If the system is located in another part of the bulding, I open a VNC session to the windows system and pull the data - its simply faster. This past weekend I started experimenting with a disk archive utility named KDAR. Although it's a KDE app, it runs fine under gnome. It archived 6 GB of data within a reasonable amount of time. KDAR compresses data so although the data transferred was just over 6 GB, it archived almost 10 GB of data. I guess what I'm getting at is that I wonder if this is a Nautilus problem. I'll have to do some timed tests using different environments to see. BTW I checked all of my settings and my NIC is set at 100 mbps/full, so this isn't a hardware configuration setting problem.

[pigpen]

I had the same problem and solved it by manually setting the duplex mode on the Windows box to 100Mbits/Full duplex.
Auto negotiation obviously didn't work...
VoidMan's advise should be honored! :)

EDIT: Well, I posted too fast. netio reports ~8MB/s whereas samba still lags at about 1 MB/s.... :(