I’ve used powerline adapters quite a bit as my previous apartments were solid concrete & rebar, they worked pretty well and from what I read, they have gotten a LOT faster since then. In terms of fixed IP addresses, again you should really need them – just use the UNC paths of the PCs (e.g. You should need to map network drives, just create a shared folder on the Synology and use the UNC path to it (\\NASNAME\SHAREName\) – provided your machines are using your local router for DNS, this should work fine. This really depends on the type of backup you’re doing, these days I generally ‘image’ my PCs shortly after a clean installation and manually copy the image to the NAS. If your NAS is operating on a private home network, you may want to disable transport encryption mode (use at your own risk) and enable opportunistic locking:įor me on my Synology DS215j, this took my file transfers from around 5MBps to around 80MBps!įor anyone looking for a better network platform for home, check out my article on Ubiquiti’s Unifi kit. In Advanced Settings, set the Maximum SMB protocol to SMB3, I also increased the minimum SMB protocol to SMB2. Login to the Synology NAS and click on Control Panel:Įnsure that the SMB service is enabled then click Advanced Settings: To find and check this, perform the following steps: Unfortunately, the file transfer speeds are so bad you’re considering buying a turtle and glueing a USB drive to its back to speed up file copying.Īfter hours of searching the net for an answer, in the end, I found the cause of my woes in a couple of little settings tucked away on the Synology – effectively my Synology NAS wasn’t even trying to use newer/faster versions of the SMB protocol. If you want better seek (random) performance, nothing beats an SSD.So you’ve got a shiny new Synology NAS and you’ve started storing files on it, videos, music and so forth.Your disk, like all consumer-grade laptop HDDs, is slow.Your disk seems to operate within specs.The write tests are usually flawed, because disks will cache writes and say "yes yes I got it" even if it's not been written to disk yet, so they're a lot more difficult to judge accurately. It also helps if several blocks are read from the same track (no seeking, and you can read the first block coming under the read/write head). For instance, the seek time is shorter when going from track 1 to track 2 than from the first to the last, so ordering the reads on increasing tracks saves time. This enables the drive to reorder the reads so they're less random. The Q32T1 test leverages queuing: multiple read commands (up to 32) are sent to the drive before waiting for the results (and as soon as a result comes back, a new read is requested, maintaining a queue of 32 pending reads).
That's for the RND4K Q1T1 read test (bottom left of your first screenshot), which is the ultimate random read test, with each read waiting for its results before getting to the next one. So the results of the benchmark are actually slightly better than theory! With 4K blocks as used by the benchmark, that's 228 KB/s, or 0.228 MB/s. Which in turn means a bit under 57 reads per second. That means that on average, reading a random block will take 17.6 ms (not counting command processing and the data transfer itself, but that's usually peanuts in comparison). Disks come in a variety of speeds, from 5400 RPM (revolutions per minute), which is quite standard for the smaller consumer 2.5" disks, up to 15000 RPM for high-end enterprise-grade disks.Īt 5400 RPM (which means 90 revolutions per second), it takes on average 5.6 ms for the right block to be under the read-write head. For this specific disk, it's 12 ms.Īverage random rotational latency is directly dependent on drive rotation speed. The platter needs to rotate until the right "sector" or block is under the read/write head ( rotational latency).Īverage random seek times are usually somewhere between 9 and 15 ms, depending on the disk. The head needs to be moved to the right "track" along the radius of the platter ( seek time).
To read a random block on the disk, two things need to happen: A hard disk drive is made of platters that turn at the specified speed, and read-write heads which move along the radius of the platter.
0 kommentar(er)
