On Wed, 3 Aug 2011 13:52:21 +0200 Steffie Morris <steffie.morris@xxxxxxxxx> wrote: > Hi, i have some questions (and problems) regarding speed in linux > using mount -t cifs for cifs shares. > > I have several ubuntu 10.10 workstations and a few windows > workstations, on wich i want to interact from one central fileshare. > At the moment i have a fileshare on a windows7 machine, and a > fileshare (samba) on an ubuntu machine. > The netwerk is 1 Gbit > From a windows client uploading/downloading to the linux samba server > i get 115 MB/s. > From a window client uploading/downloading to a windows share i get > around 110 MB/s. > From the linux client uploading to the windows share i get 60 MB/s. > From the linux client reading from the windows share i get 17 MB/s. > From the linux client uploading to the linux samba server i get 60 MB/s. > From t he linux client reading from the linux samba share i get 17MB/s. > > The biggest problem question i face, is why is reading thru a "mount > -t cifs" share this slow? > If the linux machine acts as a server the speed is really fast (in > combination with a windows client) but when i use the linux machine as > a client, the performance is not good. > Am i overlooking something? should i be using special options to > optimize performance for cifs in client mode on linux ? > I think i ruled out hardware network issue's as traffic the other way > around works (with linux as serving share), and also via FTP, or > testing with iperf gives me near full Gbit speeds. > > I tried to do some searches on speed and perfomance issues, but didn't > find anything usefull so far. > What kernel version are you using? cifs.ko is currently very slow on reads as it doesn't parallelize any of them if the reading is done via a single thread. I hope to change that in the not too distant future, but it requires some relatively major work to do it right. -- Jeff Layton <jlayton@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
