SSD, trim and Windows XP
- Thread starter FranceBB
- Start date
https://www.google.com/?gws_rd=ssl#q=software+able+to+send+trims+to+the+SSD
not my forte, but above search page may help??
not my forte, but above search page may help??
I already tried several default ones, but none of them worked. (I googled a bit before actually asking here).
But anyway, never mind.
I'm gonna use it as it is and find out.
At the very end, this SSD is just a present I received, so it doesn't matter whether I cannibalize it or not. I'm pretty confident about SSD drives and I think they are almost able to manage everything themselves.
Let's find out. I'll keep you updated!
But anyway, never mind.
I'm gonna use it as it is and find out.
At the very end, this SSD is just a present I received, so it doesn't matter whether I cannibalize it or not. I'm pretty confident about SSD drives and I think they are almost able to manage everything themselves.
Let's find out. I'll keep you updated!
okay, thanks
One trick to keep SSDs working efficiently when TRIM is not an option is to leave between 8-12 % of the drive unformatted. This gives the controller room to shuffle 'used' blocks out of service, prior to deleting them and marking them as ready for re-use.
This is mainly due to the nature of flash memory, and the way in which it works. A traditional hard drive, the instant a piece of data is deleted, will straight away report to the host system that that location is ready to be re-used. With flash, it's all down to the way in which blocks of memory (not the individual cells) are deleted, before they are able to be re-used. In other words,
1) With a hard drive, any given data location can be over written immediately.
2) With an SSD, even if a given 'block' is only half-full, say, the entire block has to be deleted, then marked as 'ready for re-use' before it can be used again.
Hope that clarifies matters a wee bit.
Mike.
This is mainly due to the nature of flash memory, and the way in which it works. A traditional hard drive, the instant a piece of data is deleted, will straight away report to the host system that that location is ready to be re-used. With flash, it's all down to the way in which blocks of memory (not the individual cells) are deleted, before they are able to be re-used. In other words,
1) With a hard drive, any given data location can be over written immediately.
2) With an SSD, even if a given 'block' is only half-full, say, the entire block has to be deleted, then marked as 'ready for re-use' before it can be used again.
Hope that clarifies matters a wee bit.
Mike.
It may be a question asked many times, but Google search produces little in the way of user commentary on whether experience has been satisfactory or otherwise. ie help in selecting 3rd party provision of 'Trim' is very lacking!
priscus - Piriform's Defraggler states that it is now able to use the TRIM function to optimize an SSD. Has anyone given this a try yet?
Here is where Piriform makes that particular claim:
https://www.piriform.com/docs/defraggler/technical-information/defraggler-and-ssds
Here is where Piriform makes that particular claim:
https://www.piriform.com/docs/defraggler/technical-information/defraggler-and-ssds
Interesting!
My need is not pressing, but I do have a spare 128 Gb SSD, which is not being used for anything currently.
May be tempted to slip it into one of my XP machines, but only if an elegant trim solution emerges, as this time of year, I have a lot to do: no time to go off at a tangent on any additional problem solving projects.
My need is not pressing, but I do have a spare 128 Gb SSD, which is not being used for anything currently.
May be tempted to slip it into one of my XP machines, but only if an elegant trim solution emerges, as this time of year, I have a lot to do: no time to go off at a tangent on any additional problem solving projects.