Kingston Intros V+100 SSD with 'Always On' Garbage Collection



+ Add a Comment


Right now there is no native TRIM support in Win7 once you RAID the drives. Intel announced something about a version of TRIM beeing available in the next version of their Matrix storage manager, but i have not heard any more about that since March 2010.

I even saw a rumor that an upcomming version of Indilinx would support TRIM through a RAID, but once again, it was a rumor and I haven't heard any more about it.



Well, Sandforce has its own garbage collection routines, and it's the premierfe SSD controller right now. I imagine a lot more drive makers will start to include their own trash algo's with their next generation chips and largely make the question of TRIM commands from the OS moot in a year or so (or so we could all hope, since we're starting to see less consisten OS deployment and a lot more alternatives like linux, android, chromium, etc that could all run on a desktop with an SSD) The real question I have is, why would you want to use a PCIe sollution when there's SATA III on a lot more boards, most of which don't even support "boot from PCIe" yet regardless of whether they have SATA II, III, or other.


Bullwinkle J Moose

Because I'm just not happy untill I complain about something!


Great idea but all SSD makers should also correct the partition alignment in firmware as well (if possible)

We need our SSD partitions correctly aligned automagically when we set them up in XP!




Keith E. Whisman

Looks like it's cheaper to purchase two 256GB drives and run in Raid 0 compared to that one 512GB drive. A good question would be, does the Trim function work while the drives are in Raid 0.


Peanut Fox

No.  It doesn't work.



This question just came to me: What capacity does Windows say these SSD drives are? I run a 300GB Velociraptor, WIndows says it is 279GB. Does the same hold tru for a SSD?



I would assume that they report the same way that that platter drives do. Meaning that 120 gigs on the box actually equals about 111 gigs; since drive makers use Gibibytes while operating systems parse gigabytes. A gibibyte = 1000 megabytes as opposed to a gigabyte = 1024 megabytes. (plus OS overhead and FAT tables)



Actually it's the other way around.  Gibibyte would be base 2 or 1024 Mebibytes while Gigabyte is base 10 or 1000 Megabytes.



Actually the 1024 is referred to as *byte and 1000 is *bit. You don't have Gibibyte ethernet it is Gigabit ethernet. 1024 is storage block measurements and the 1000 is transfer measurements.


* = kilo, mega, giga, etc...



thank you for the correction. Still, it remains true that drive advertising math and OS math remain different. but it's not base 2, it's base 8, based on octohedral, each individual character or function is based on an 8 place binary character or bit; so 8, 16, 32, 64, 128, 256, etc. which is where the discrepencies between drive math and OS math. one is decimal, one is octohedral.

and of course if you read Douglas Adams, you're familiar with base 13 :D

Log in to MaximumPC directly or log in using Facebook

Forgot your username or password?
Click here for help.

Login with Facebook
Log in using Facebook to share comments and articles easily with your Facebook feed.