All this raises an interesting question: How much effort is it reasonable to expect a user to undertake just to use one of these drives? I mean it's going to be very tough to argue that it should require more than "plug in -> add partitions > boogie" I mean half of what I'm hearing about how to set these up sounds like superstition based on how flash was 10 years ago. =\ I mean there needs to be a protocol where the drive communicates with the operating system what it needs, and the OS should just do it, and the user shouldn't know about it prior to running utilities on the volume/drive...
It is really not reasonable to expect the user to know, understand, and actively administrate delicate tuning parameters for specific makes and models of drives and evolving tools to use these drives. Right now my drive is set up as if it were a black box that contains bits. I don't think it's reasonable for me to do anything more than that. =\ Daniel Frey wrote: > On 02/13/2017 10:25 PM, Mick wrote: >> I was using discard and can't say I >> noticed any performance penalty on the OCZ drive. I removed it and set up a >> fstrim cron job and suddenly there is a major I/O bottleneck when the cron >> job >> runs. Perhaps I should be running it more often ... >> > Yeah, I read something that recommended weekly fstrim but it was > noticeable. I found doing it more frequently (I set mine up to daily. Or > was it twice a day?) it doesn't take as long. > > Also make sure that the job runs if it's missed. -- Strange Game. The only winning move is not to play. Powers are not rights.
