Jump to content
Corsair Community

Low score on AS SSD. ACHI already on.


Recommended Posts

Ok so I've had this ssd installed on IDE for awhile now but am just deciding to get around to trying to increasing performance. First I did the reg fix to change my bios to achi on without doing a fresh install of Windows. I'm still getting low results. So I went ahead with a fresh install of Windows with achi on. Still with low results. I'm on my phone, otherwise I would post a screen shot but my read speeds are around 170 with a write speed of 72ish.

 

suggestions? I'm out of ideas here after the bios settings being on achi and a fresh install of Windows.

Link to comment
Share on other sites

Here is the atto results. Just so I am understanding this correctly, the speeds are showing as 457 megabytes for writing and 546 megabytes for reading? That is around the targeted rates for this ssd but why was as ssd so WAY off?

 

http://imgur.com/ENOyrhK.png

Link to comment
Share on other sites

Im repeating it on and on again: YOu have to setup AHCI in the BIOS!!!

Considering this is the Force 3 (60GB) the speeds are good.

Low ASSSD-results is normal since Corsair make up the specs with compressed transfers (ATTO), this is a common "hoax" of SandForce-drives.

You expecting around 500mb read/write overall is BLOW CAKE!

 

You even never encounter cases where you would need such rates.

 

And it doesn't matter, because it has ultra-fast rates on small files plus a ultra-low response-time to kick off any HDD as OS/App-drive.

 

PS: Dont repeat benchmarks, that will not make it faster but slower ... forever!

Link to comment
Share on other sites

Im repeating it on and on again: YOu have to setup AHCI in the BIOS!!!

Considering this is the Force 3 (60GB) the speeds are good.

Low ASSSD-results is normal since Corsair make up the specs with compressed transfers (ATTO), this is a common "hoax" of SandForce-drives.

You expecting around 500mb read/write overall is BLOW CAKE!

 

You even never encounter cases where you would need such rates.

 

And it doesn't matter, because it has ultra-fast rates on small files plus a ultra-low response-time to kick off any HDD as OS/App-drive.

 

PS: Dont repeat benchmarks, that will not make it faster but slower ... forever!

I apologize if I didn't make it clear enough in my initial posting but I DID set up achi in the bios

Link to comment
Share on other sites

I need to add the following for informational reason:

 

From what i see in your ATTO screenshot is not only read 546 MB/s / write 457 MB/s but:

 

@1024K-max.Write: 470,1 MB/s

@4096K-max.Read: 560,5 MB/s

 

Corsair specifies the disk as follows:

Max Sequential R/W (ATTO)550 MB/s sequential read — 490 MB/s sequential write

 

But you want to know why ASSSD is so low, i explain it to you in detail:

 

What corsair and all other sandforce-resellers measure as maximum rates is in detail the rate at which your SSD can sequentially read/write one single maximum compressable file chunk up to a size of 8 Megabytes. You tell the software to measure 256MB sizes at all, but that only means in case of "8192" it checks 32 runs measuring a single 8 MB file-transfers read/write and showing you the highest. So these high rates are only guaranteed for small files. This barely doesn't really mean "sequential" at all from my point of view, but thats politics.

 

What ASSSD and CrystalDisk do for testing sequential read/write is test a larger file probably minimum 50MB of uncompressible data... because this is what you expect in real-life. To accomplish that the sandforce-controller internally devides the "file" into smaller chunks and addresses as much as possible simultaniously and externally process them one after another to the Serial-Bus (no parallelism allowed).

 

We dont know how the things are happening on the controller FW (propriety), whats the SF-Controllers exact capabilities (processing power unknown, cache-size unknown).

 

But what we know is:

A) This isn't very effective by design at all, so the controller needs to be powerful. (Parallel-Bus'ing was BS for HDD but would be nice for SSD)

B) Because there is no way in compressing real-life data that much, physical-capability doesn't mean practically-achievable.

 

So I recapitulate: You can physically write 1MB files with 470 MB/s, read 4MB files 560 MB/s on a briefly good controller, that is very good. Don't worry about low sequential continguous read/write of real-life data. ~90-100 MB/s seq write and ~180-200 MB/s seq read is good for this drive, it outperforms nearly any 7200RPM HDD and for an OS/App-Drive continuos seq. read/write doesn't matter that much, because most of the stuff happening is of <= 8MB size.

 

But non the less, your small chunks 0,5 - 8kb transfer rates are way to slow, even for the AMD-Controller. Looks like MSAHCI-driver

 

Please install latest SATA-Driver from your vendor.

AMD-Sata-Driver click here

 

PS: For the raid-nerds, whatever ATTO shows you 1GB/s ... practically you'll be stuck here too.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...