Solid-State Drives (SSD)

[Weeblie]

http://www.crucial.com/store/partspecs.aspx?IMODULE=CT64M225

http://www.crucial.com/store/partspecs.aspx?IMODULE=CT128M225

http://www.crucial.com/store/partspecs.aspx?IMODULE=CT256M225

64 GB: 200MB/s READ, 150MB/s WRITE

128 GB: 250MB/s READ, 190MB/s WRITE

256 GB: 250MB/s READ, 200MB/s WRITE

I'm not sure how much clearer it can be.

[targetbsp]

@Kallagon - how much writing to the disk?  The performance is still fine this morning after a couple of hours general use (surfing the net, playing warcraft) with an s3 suspend in the middle.  And however much writing the benchmarks themselves do.  I don't wanna do many unneeded writes cause I don't have trim supporting drivers yet so my write speed will suffer from that.

[kallogan]

"I'm not sure how much clearer it can be"

Yep my mistake. I guess i didn't pay enough attention to the individual specs. I just read some reviews, that's all, and didn't notice that size matters that much back then ;-) Anyway, even the 64GB version is sooo much faster than my old HDD, i'm quite happy with it...with 1571 of course ;-).

@target

Hope your speeds will remain the same.That would be a good news.

Personally speaking i don't want to restrict myself. I installed lots of stuff and did a dozen of benchmarchs since i'm back on 1571 and speeds are still the same like in the old time.

[johnyeah2]

I'm wondering what is the actual benchmark speeds I should be getting with my 128GB SSD? When I run crystaldiskmark after performing a wipe, my sequential read/write are 190 mb/s and 90 mb/s. I thought the performance should be slightly higher than that? Any inputs? Or am I just experiencing the same problems everybody else is with the 1819 performance drop?

[sonicsonic]

I got this results on 1819fw after wiping the drive with c_wiper and clean install without the 100 MB rescue partition.

2 ssd's x128 gb b

first i ran wiper the first drive was fast like 5 Min's the second 1 took ages to complete so i disable the no execute memory protect and made the 2nd drive active partition rebooted the wiper ran perfectly,with the flowing results

win 7 home 32 bit

trim enabled /ide mode -bios

ep45-ud3p+9550 on 4.0ghz

------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                first drive 10% filed                                                   second drive 40% filled
------------------------------------------------------------------------------------------------------------------------------------------------------------------

[targetbsp]

I never seem able to see the pictures on this forum when people first post for some reason.  Then they sort of work several hours later. :s So I've no idea what sonics results are atm!

@johnyeah your crystal figures look the same as mine but the 128 should be faster.  From a quick glance at some review sites you should be getting approx 240mb reads and 140mb writes in crystal (which seems to benchmark writes slower than atto and hd tach - I didn't realise this until last night so people upset with your write scores make sure you;re not compating your crystal scores with others atto/tach scores).  Have you tried the wiper reboot wiper reboot thing Katana suggested?

[sonicsonic]

i reap loaded the pic again sorry dint knew its and issue with pic's

yes i did the same operation Katana said

do i get good speed?

also real test comes after few days of use and install of all apps that i been missing

but with trim enabled i see no reason why it should drop?

[Fred]

Crucial Katana,

Here is what I don't understand:  If the 1819 Firmware enables Windows 7 TRIM  to wipe the SSD, why would it be necessary to use the Wiper tool?  Does TRIM work in Windows 7?

Fred

[mcnaugha]

I would presume it's because TRIM isn't a garbage collection tool. It won't retrospectively/automatically go through the blocks on your SSD and clean them out for you if they contain data. So if you've got dirty blocks, just because TRIM is safe to use now it will only take care of new deletes/erases.

[Fred]

mcnaugha,

I hear ya, but the problem is that the original poster installed on a new, clean SSD.  It then only hand new deletes and no old blocks filled with garbage.  Also, he didn't disclose whether he was doing a lot of deleting.  He said that he had the slowdown after installing his other applications and running for a while.  That's my reading, anyway.  So, it appears as though your analysis, though logical,  doesn't apply here. Is this not correct?  Anyone else?

Fred