Optimise for SSD's. Has anything recently changed?

"
My solution ; service Op. Drives on manual , once a month trim your SSDs manual .
This is the most safe way for your precious hardware ! "..................whats wrong with this solution ??

I'll think about it. Wrong end of the day now

pietcorus2 said:

service Op. Drives on manual , once a month trim your SSDs manual .

Click to expand...

Do you mean to untick the scheduler and just run manually from the Optimise Window?



Before I do anything like that, I want to make an incremental backup first and then another one afterwards as doing that shows (to me anyway) that something really has happened.

I'll look in tomorrow... and think about it

" Do you mean to untick the scheduler and just run manually from the Optimise Window? ".................yes , best way for keeping your SSDs at maximum health !
Trimming once a month is just fine , more then once is too much .............

pietcorus2 said:

" Do you mean to untick the scheduler and just run manually from the Optimise Window? ".................yes , best way for keeping your SSDs at maximum health !
Trimming once a month is just fine , more then once is too much .............

Click to expand...

Once a month may be fine, but there is absolutely no problem doing it more frequently. Even if you ran it every hour, there would be zero negative effects. Yes, doing it every hour is not what anyone is likely to do in real life, but it makes the point.

pietcorus2 said:

Trimming once a month is just fine , more then once is too much .............

Click to expand...

I'm not convinced in all this you know......

I've done as you suggest and set and run a manual Optimise routine. Left it a while, done a restart and made a second incremental image. I know you must be thinking 'what has all this image file talk got to do with anything' but I've noticed in the past (and posted somewhere) that running a manual Optimise doesn't seem to do anything but when it does run on schedule the changes (in file size) are pretty massive.

Anyhow... I've run it manually but have no proof anything has happened or that it has done what would happen with a scheduled run.



This is what I mean by file size changes. The difference between the new image and the one before optimising is minimal.

Also... and this interesting... I checked now my now much less used PC also running W11 (fully updated) and that has gone something like 39 days since the last Optimise run. Something has changed (maybe some systems are affected differently) but what.

So you mean ; we have to set the Optimise-service on auto , coz its better for SSD-lifetime..............??

I don't think anything is affecting SSD lifetime, I just have a suspicion that running manually like I have just done hasn't actually done anything at all.

It says it has run when you do it manually... but is that message 'just to keep the customer happy'. I honestly don't know; and this is what bugs me over this issue.

Well , running a Samsung SSD , from 2015 , Win7 , Win10 , now on Win11 ............always , 7 years the Optimise-service on manual , never had wear-out problems and this SSD is on 95% still.............

I've just found this:

It looks to me like something has broken (maybe with an update)

I can see from clean installing that it ran on 22 Sept, 29th Sept, 30th Sept, 1st Oct, 7th Oct, 20th Oct, 21st Oct, 22nd Oct and then nothing for the main C drive but the others are being done super often, sometimes twice a day.

" It looks to me like something has broken (maybe with an update) "................like I said before, just keep it manual , MS-bugs wont affect it anymore...............

It is not surprising that TRIM has run less often on the C:\ drive, it is almost constantly in use even when the PC is 'idle', log files created/ updated, memory paged/ cached/ released and so on, the drives controller will delay TRIM if the drive is too active.
Also remember that TRIM is a function of the erase/ write cycle and the optimise function is a re TRIM command.

Regardless of whether the utility does anything or not it would not alter the image size, something else is responsible for that, image software will not include 'marked as deleted but still containing data' blocks so running a TRIM command before the image creation has no effect on the final image.

If you want to see what the TRIM command is doing then stop the app from running on a schedule for a while and use PowerShell with verbose reporting, as I suggested in an earlier post. It will give you a report of the number of items processed, the number ignored and other results that you can save for later reference to compare operation over time.

Example PowerShell TRIM commands:
Optimize-Volume -DriveLetter C -ReTrim -Verbose
Optimize-Volume -DriveLetter C -Analyze -Verbose

DigitalGoat said:

f you want to see what the TRIM command is doing then stop the app from running on a schedule for a while and use PowerShell with verbose reporting, as I suggested in an earlier post.

Click to expand...

Thanks, that could be useful. I might just do that.

DigitalGoat said:

Regardless of whether the utility does anything or not it would not alter the image size, something else is responsible for that, image software will not include 'marked as deleted but still containing data' blocks so running a TRIM command before the image creation has no effect on the final image.

Click to expand...

That this happens (massive file size increase following an Optimise) is something I have noted on many occasions in the past (W10 as well as 11) that I have to say it is a real effect. It happens.

So , again , this means we have to set the service on auto . (??)
Still dont know whats best for SSDs in use ( life-time!) ; set service on auto /manual .
Its a well known fact , several bugs were reported in the past , all related to MS............

pietcorus2 said:

Still dont know whats best for SSDs in use ( life-time!) ; set service on auto /manual .

Click to expand...

You could run a retrim a thousand times a day and it will make zero impact upon the life of the SSD. That's simply not how it works.

hsehestedt said:

You could run a retrim a thousand times a day and it will make zero impact upon the life of the SSD. That's simply not how it works.

Click to expand...

Then WHY (?) on auto , if this setting will trim several times a day , without any impact for lifetime ?
So , keeping it on manual and trim once a month is sufficient , will cost us less memory , etc , also..............

fruh said:

My 2 SSDs optimization is set to weekly but I've checked and it hadn't been run in 30 days (and was marked as needed lol). I've had this issue for ages and it's still there

Click to expand...

I dont want to start a optimization war here by this, but ive read somewhere that outside of scheduling optimizations windows will run on its own if its ever even needed. Disc optimization 3rd party apps are NOT supposed to be good to use according to my findings. BUT. If I am mistaken please correct me or link me to a professional article explaining why they would be good to use. Ty

Just to keep this thread up to speed I have done as @DigitalGoat posted and run the routine from Powershell. I also did an 'Analyse' first and only the C drive had a few fragmented files. The others showed no fragmentation (if you can have such a thing on an SSD)

So all done and I've re enabled the scheduler to see what now happens. I can always go back if needed.

Mooly said:

So all done and I've re enabled the scheduler to see what now happens. I can always go back if needed

Click to expand...

Continuing on from this and today a retrim occurred. The D partition is on the same drive as C and has seen no change in content and that partition has not been optimised... which is logical.

The other two partitions are on another internal drive and M gets lots of big changes as backup files are deleted. F only gets little additions made and so should not really need optimising. Perhaps 'additional' drives like this can only be done as one, or are only done as one should I say.

I shall keep a watch on future behaviour.

After reading all these replies still convinced the manual method is best !
So , service on manual and once a month a trim on SSDs .
My ( OS) SSD works perfectly since XP with this method.................