2013/10/18 matthew patton <[email protected]>: > 5. What is the underlying spinning RUST and SSD configuration? A 7K RPM drive > can barely muster 100 random IOPS. The SSD can obviously do vastly better on > reads but writes can vary all over the map depending on how the firmware's > smarts and filesystem/block layer coalesce capabilities. Please describe the > model of SSD and HDD being used. > > 6. OS level scheduling (should be noop or deadline) can influence behavior > and block level read-ahead should be turned off on the SSD in particular. If > you can get the FS to journal in nice, big chunks (eg. erasure block size of > commonly 512KB, intel used to use 128KB) that helps too.
Thanks again. I'm switch to lvm logical volumes for vps. Scheduler deadline.What i can tune now to not crack ssd =)? As i known i can switch sequential_cutoff to default? -- Vasiliy Tolstov, e-mail: [email protected] jabber: [email protected] -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
