I'm looking into this.
1 of 1 people found this helpful
I don't have anything specific to report. Our internal tests on Win 7 shows the optimizer completing in about 40 seconds so I think your 1 minute completion time is not out of the ordinary.
My work system has a 120 GB 320 SSD and optimization completes in about the same 10 seconds.
I think the difference is the drive size and the over-provisioning on the DC S3700.
Is there any possibility that you could run the optimization after the rest of your start-up routine and logging?
Thanks for looking into this. We ultimately had to change our software so that we wait before accessing the SSD until after the Optimizer utility is completed.
We had two issues
1) When trying to write to a file we got a "memory access violation" when creating and writing to a file on the SSD being trimmed.
2) We lost data that was written to a new file while the Optimizer routine was being run.
We found a work around for both of these but I believe there are issues when creating and writing to files while the optimizer is running that you will need to address.
Paul (formerly u_p)