Page 2 of 2
Re: TRIM
Posted: Mon May 27, 2019 10:17 pm
by Brian K
The disk is a SSD. Intel 535 Series 480GB.
I did some more tests today, in this order...
Microsoft Optimizer of C: drive..........2 seconds
Intel Toolbox...............................10 seconds
BIBM PartWork Trim...................... 12 minutes
BIBM PartWork Trim of a clean 1903 install... 20 seconds (same SSD)
Re: TRIM
Posted: Tue May 28, 2019 5:33 am
by TeraByte Support
I'm sure it's probably fragmentation. The command is sent to the drive and
the drive takes it from there, so if it has to send a lot of commands,
that's where all the time is. So a delete with trim would be quick
because only limited by max size allowed for trim.
"Brian K" wrote in message news:17183@public.bootitbm...
The disk is a SSD. Intel 535 Series 480GB.
I did some more tests today, in this order...
Microsoft Optimizer of C: drive..........2 seconds
Intel Toolbox...............................10 seconds
BIBM PartWork Trim...................... 12 minutes
BIBM PartWork Trim of a clean 1903 install... 20 seconds (same SSD)
Re: TRIM
Posted: Tue May 28, 2019 6:20 am
by Brian K
TeraByte Support wrote:
> I'm sure it's probably fragmentation.
Thanks but I didn't think fragmentation applied to SSDs. Anything I can do about it?
Re: TRIM
Posted: Tue May 28, 2019 4:34 pm
by TeraByte Support
It would just be issuing a bunch of commands.
"Brian K" wrote in message news:17185@public.bootitbm...
TeraByte Support wrote:
> I'm sure it's probably fragmentation.
Thanks but I didn't think fragmentation applied to SSDs. Anything I can do
about it?
Re: TRIM
Posted: Tue May 28, 2019 8:24 pm
by Brian K
This helped. I restored today's image with the "Compact Data" option. Now BIBM PartWork Trim takes 15 seconds instead of 12 minutes.