Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
The Windows-driver for Intel ICH10 doesn't distribute reads over the disks, while at least the Linux md-driver does. I don't know about the RAID-function in Windows 7/8 Professional+, maybe someone can jump in here. Read speed in systems that distribute requests should be appr. 1.8x of the write...
Spun up hours has nothing to do with MTBF. Even while the disk is spun down, the whole "system" called "harddisc" is up - so this has nothing to do with MTBF - maily with energy saving (and a bit of more quietness of course).
And very good. The maximum you could get from 11n is appr. 100mbit OTW. You should ise a tool like inSSIDer to see the networks in your neighbourhood and maybe you can select a channel that fits you better. Check the channel usage near your AP and where your computer is located as there might be...
So far what I found out helps Samba (on my linux-system, you results may vary):
Turn off CPU frequency scheduling or set the governor to performance. This increases throughput considerably (20% on both r/w here)
Try changing your adaper offload-settings in Linux (ethtool -k eth0). Your mileage...
# of cores don't matter is mostly right.
see a quad running at 25% (or even 30%) cpu utilization: what you can most probably argue is that just 1 core is used - what task manager shows is something that is greatly falsified by windows, because the OS switches cores "as it thinks to be best"...
If you do have 10.04 (that's what I tried it on), this is straightforward:
sudo add-apt-repository ppa:polslinux/ppa
sudo apt-get update
sudo apt-get upgrade samba
sudo apt-get dist-upgrade
then add "max protocol = SMB2" to your smb.conf, and voila.
This is totally independent of the kernel, just the version of smbd is relevant.
This absolutely adds up, it's the latency of the ACK-packages, something that is addressed in SMB2. This especially drops in in High-Speed WiFi environments, where SMB2 gets a huge win above SMB1. Note with my...
Well here seems to be a bit of confusion and also superficial knowledge, so I post some benchmarks with a bit of explanation here (the dd-type test is rather good, because you can tune a bit, so later more):
The Server is an AMD Athlon 64 X2 Dual-Core machine with 1GB RAM (yes, only), a Realtek...