• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Yeah! SSD!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Would really love an answer/opinion to the above question, which is somewhat unrelated to this thread lol

Sent from my HTC Eva 4G using Tapatalk
 
But if I shrink it without extending, post install, wouldn't that be the exact same thing? The extra space would become unallocated I thought. I'd really like to avoid reinstalling if possible.

Elimination of logical mapping(parititons) will increase efficiency of SSD for more than just lifespan alone. Some controllers will respond better than others, but all will see some type of write-speed stamina/IOPS increases.

Easiest way, if it's an afterthought, is to just shrink the partition in disk mgmt. Once you shrink the volume down from fully allocated space.. the controller will compare maps and immediately know that the previously allocated space can be cleaned up and set aside for larger fresh block reserves. Doesn't necessarily mean that the controller will jump right into that task.. just that it will know it has full control for whatever it deems fit to use it for.

I would always logoff idle any SSD based machine that's recently had a partition shrunk down(trim or no-trim) for at least 4 hrs straight since that's what GC is for.
 
Elimination of logical mapping(parititons) will increase efficiency of SSD for more than just lifespan alone. Some controllers will respond better than others, but all will see some type of write-speed stamina/IOPS increases.

Easiest way, if it's an afterthought, is to just shrink the partition in disk mgmt. Once you shrink the volume down from fully allocated space.. the controller will compare maps and immediately know that the previously allocated space can be cleaned up and set aside for larger fresh block reserves. Doesn't necessarily mean that the controller will jump right into that task.. just that it will know it has full control for whatever it deems fit to use it for.

I would always logoff idle any SSD based machine that's recently had a partition shrunk down(trim or no-trim) for at least 4 hrs straight since that's what GC is for.

Are you suggesting that SSD firmware "understands" partition layout? That seems like a dangerous road to travel for SSD mfgs, there's a lot of OSes, and partition layouts. For example, NetBSD's "disklabel", uses a database that is seperate from the standard PC MBR layout.
 
Are you suggesting that SSD firmware "understands" partition layout? That seems like a dangerous road to travel for SSD mfgs, there's a lot of OSes, and partition layouts. For example, NetBSD's "disklabel", uses a database that is seperate from the standard PC MBR layout.

No.. not at all. Just that data mapping and the way that the controller makes use of it's physical space is improved on all SSD when OP is implemented.

A smaller map reduces controller overhead. Simple as that. :thumbsup:
 
Back
Top