Best "Bang/Buck" SSD?

toddw

[H]ard|Gawd
Joined
Sep 9, 2004
Messages
1,459
Hey all, I'm still running two 32GB old school raptors. Is the time ripe yet for me to get on the SSD bandwagon? The thing that's holding me back is I don't need tons of storage. 64GB in raid is all I need... but speed, speed is always good.

What is the best bang for the buck SSD?
1) I want to feel a noticeable improvement for my $$ over old school raided raptors
2) Don't want to spend the $400 I've seen on some models
3) I want it to hook up like a normal sata drive, plug and play, etc

OR... this is a want not a need... should I hold out another year for the new tech?

Thx
 
If you are willing to wait there are a lot of rumors that there will be large price drops in the second half of the year. I am waiting and hoping myself, because I am not going to pay current prices for one.
 
A pair of OCZ Vertex 30GB SSDs in RAID should be more than enough and would run you <$200 after MIRs. Would be freakishly fast. :)
 
An 80GB Intel 25X-m can easily be had for under $200 on eBay. I paid $185 shipped for mine last summer. I suspect you can do better than that now.
 
Problem is TRIM isn't supported with RAID drivers. So while your sequential reads & writes will be super higher even after the the slow down kicks in (which will happen fast on only 60Gb of drive space) your random reads/write which don't really go up much with RAID will degrade after some time, so your actual real world performance could be lower than a good single drive with TRIM. Also since most places say you should keep 20% of drive empty (or unpartitioned) for best performance, 60Gb size could also be a limiting factor. By the time you also add in the binary conversion your actual usable space your down to like 45Gb

I know you probably plan on putting some storage on other drives, but then that stuff will be slower, which defeats the whole purpose of having an SSD!

My recommendation would be to get an X25-M 80Gb G2 for now.... and down the road when/if Intel releases new drivers that support RAID pick up a 2nd one for RAID 0.


INTEL: 80Gb x 93% (binary translation) x 80% (max use/20% free) = approx 60Gb of real use.
vs
OCZ: 60Gb x .93 x .80 = 45Gb
 
Thanks all. Saw some info on Q4 drives. I'll wait. $200 for the same space, even at twice my current speed just doesn't seem worth it. Appreciate your comments/suggestions.
 
I'm curious why so many people don't seem to get the idea of using separate drives for everything.. Not everything is meant to go on the SSD.. You aren't buying space you're buying .01 access times.
 
I'm curious why so many people don't seem to get the idea of using separate drives for everything.. Not everything is meant to go on the SSD.. You aren't buying space you're buying .01 access times.

Yep. I'm obviously with you river22.
My set up:
1x X25-M 80Gb G2 for OS & Apps
2x WD 640Gb Black in Raid 1 for data storage, and maybe some big game installs.


Get whatever SSD you can afford for your OS and key apps.

Then throw everything else on a modern 500+ Gb drive and you're set.
 
That was how I was looking at it. For an OS/Key app drive its all about the random access times right? Not much to do with sequential reads/writes? I'd love to see just how fast Eclipse loads on a nice SSD. It takes 5 minutes on meh schools comps..1 minute on mine.
 
your random reads/write which don't really go up much with RAID will degrade after some time, so your actual real world performance could be lower than a good single drive with TRIM.
Random IOps does increase with a properly setup RAID0, but there's much that can go wrong:
  • Windows XP uses 63-sector offset partitions that cause misalignment on RAIDs and SSDs alike; causing lower SSD lifespan and destroys any IOps benefit from RAID0.
  • Stripesizes below 128KiB will cause multiple disks to be involved in a single I/O operation, thus destroying the IOps benefit from RAID0.
  • In the case of PCI the parallel I/O has much added latency because multiple I/O requests will have increased latency, lowering the benefit from RAID0 on random I/O
  • Benchmarks may use only a queue depth of 1, while higher queue depth is needed to allow RAID0 to use multiple drives in parallel
  • Applications that use blocking I/O may be stuck on a queue depth of 1, meaning you get single disk performance from RAID0 during that time, if the I/O is not contiguous.

In other cases, a proper RAID0 would see increased IOps. As the IOps are not spread evenly on all RAID member drives; the increase is not linear; but at least in theory IOps would double when the number of disks double.

To cope with no TRIM, simply create a partition smaller than the full capacity. The unused space is actually used by the SSD to accelerate random writes. As long as this pool of reserve space doesn't run out, your performance will be on-par and you don't really need TRIM.

TRIM is useful so the SSD knows that some data blocks on your filesystem are actually unused, so:

TRIM + 100% partition with 10% unused space on NTFS-filesystem = 10% free blocks for the SSD
TRIM + 90% partition with 0% (doesnt matter) unused space = 10% free blocks for the SSD

So with TRIM, you can use the full capacity of your drive, while without TRIM, you would have to create a partition smaller than the full capacity; to make sure the SSD has free cells.
 
I'm curious why so many people don't seem to get the idea of using separate drives for everything.. Not everything is meant to go on the SSD..

I've been using that configuration long before SSDs arrived.

Put the OS and programs on the "current" (Raptor, VR...whatever) little screamer drive and everything else in storage.

Works for me and makes those OS screw-ups much more tolerable. :)
 
newegg has the G1 80GB X-18m on sale for 150$ and free shipping. G1 does not support trim, but does keep the drive in a semi-new state with its own garbage like collection function.
 
Ended up returning a 64GB SSDNow , what do you guys think the best SSD
for under 140 bucks is? I thought I needed a 64 for the space,
but I think a 30/40gb would do just fine. Is it worth it to spend the extra
dough and get the 80gb intel?
 
Random IOps does increase with a properly setup RAID0, but there's much that can go wrong:
  • Windows XP uses 63-sector offset partitions that cause misalignment on RAIDs and SSDs alike; causing lower SSD lifespan and destroys any IOps benefit from RAID0.
  • Stripesizes below 128KiB will cause multiple disks to be involved in a single I/O operation, thus destroying the IOps benefit from RAID0.
  • In the case of PCI the parallel I/O has much added latency because multiple I/O requests will have increased latency, lowering the benefit from RAID0 on random I/O
  • Benchmarks may use only a queue depth of 1, while higher queue depth is needed to allow RAID0 to use multiple drives in parallel
  • Applications that use blocking I/O may be stuck on a queue depth of 1, meaning you get single disk performance from RAID0 during that time, if the I/O is not contiguous.

In other cases, a proper RAID0 would see increased IOps. As the IOps are not spread evenly on all RAID member drives; the increase is not linear; but at least in theory IOps would double when the number of disks double.

To cope with no TRIM, simply create a partition smaller than the full capacity. The unused space is actually used by the SSD to accelerate random writes. As long as this pool of reserve space doesn't run out, your performance will be on-par and you don't really need TRIM.

TRIM is useful so the SSD knows that some data blocks on your filesystem are actually unused, so:

TRIM + 100% partition with 10% unused space on NTFS-filesystem = 10% free blocks for the SSD
TRIM + 90% partition with 0% (doesnt matter) unused space = 10% free blocks for the SSD

So with TRIM, you can use the full capacity of your drive, while without TRIM, you would have to create a partition smaller than the full capacity; to make sure the SSD has free cells.

Doesn't the random writes max out (on small size files) b/c of the stripe size, and the min. block size. B/c your I/O's are pretty much maxed out too.
As an example if you look at people's CrystalDiskMark score, the 4k random read & writes stays about the same, even though the sequential read/writes double in performance with Raid 0.

Basically, the stripe size down doesn't benefit when going from single drive to Raid 0. So if stripe size = 64kb the performance for random read/writes of that size & down is very similar as a single drive.
 
I'm curious why so many people don't seem to get the idea of using separate drives for everything.. Not everything is meant to go on the SSD.. You aren't buying space you're buying .01 access times.

Yeah, the way I see it, you pay $220 (or w/e) to speed up your OS/apps and maybe some game load times if you can fit a few in... Just as most people will pay $200 for a quad core when they probably don't need it for 80% of what they do and would be just as well with a $100 dual core... :p The SSD has more of an impact on overall system responsiveness than the two extra cores do but most enthusiasts don't bat an eye at paying for those quads (or paying for 8-12GB of RAM for that matter). /shrug

Ended up returning a 64GB SSDNow , what do you guys think the best SSD
for under 140 bucks is? I thought I needed a 64 for the space,
but I think a 30/40gb would do just fine. Is it worth it to spend the extra
dough and get the 80gb intel?

I'd go minimum w/a $120 40GB X25-V, preferably a 60GB Vertex/Agility for like $10 more... Dunno why you would spend more on a Kingston (JMicron or Toshiba) drive that doesn't perform as well as those. It's all a matter of how much space your apps take up, I do fine w/40GB on my netbook. /shrug Still got some room for movies & off-loading photos.
 
Back
Top