search for: cifsv3

> Limiting the linux-server's max cpu-speed had > the most affect on performance: > (limited to 1.6GHz instead of 2.4GHz) (33% limitation) The server is equipped with an 6 core / 12 tread 3.6 GHz CPU (Intel Core i7-980x   and  a Raid 10 Disk array. The cpu is 90% idle (including webserver traffic and mailserver traffic) during downloads. There is no encryption because the samba VM

...f 2.4GHz) (33% limitation) >> > The server is equipped with an 6 core / 12 tread 3.6 GHz CPU (Intel Core > i7-980x and a Raid 10 Disk array. > The cpu is 90% idle (including webserver traffic and mailserver traffic) > during downloads. > --- In protocols before cifsV3, only 1 tcp connection was allowed between a user at workstation and a server. So multi-cores make no difference. When you say "the cpu is 90% idle", you realize that means 10% busy. 10% * 12 cores = 1.2 cores busy. That may imply one core is "pegged". Though it sounds...

...; The server is equipped with an 6 core / 12 tread 3.6 GHz > CPU (Intel > >> Core i7-980x   and  a Raid 10 Disk array. > >> The cpu is 90% idle (including webserver traffic and mailserver > >> traffic) during downloads. > > --- > >    In protocols before cifsV3, only 1 tcp connection was > allowed between > > a user at workstation and a server.  So multi-cores make no difference. > Ok this clarifies why two downloads are getting more bandwidth than 1 > > > >    When you say "the cpu is 90% idle", you realize that means 1...