1 2 Previous Next 17 Replies Latest reply on Mar 3, 2010 1:15 PM by ambizytl

    Weird SSD Benchmark

    jznomoney

      Evertime I benchmark my intel 160gb G2 ssd drive I get a weird benchmark like this in the image.  Is this normal?

      graph.png

        • 1. Re: Weird SSD Benchmark
          ambizytl

          I believe it is normal, though I haven't used HD Tach in a long time. The benchmark tool designed specfically for SSD is AS SSD: http://www.alex-is.de/PHP/fusion/downloads.php

          • 2. Re: Weird SSD Benchmark
            jznomoney

            so does this look right?as-ssd-bench INTEL SS DSA2M16 2.14.2010 11-03-58 AM.png

            • 3. Re: Weird SSD Benchmark
              ambizytl

              Your 4K-64Thrd looks a bit low as does your overall score. Have you updated to latest firmware? I have an older version of AS SSD and this is one of the tests I ran (test results do vary).

               

              The driver you are using is not the same as my driver. You need to run optimizer when not using msahci default AHCI driver. Are you running in AHCI mode?

               

              as-ssd-bench INTEL SSDSA2M160 1.3.2010 4-16-21 PM.png

              • 4. Re: Weird SSD Benchmark
                jznomoney

                I have an AMD 780g motherboard using the amd AHCI driver.  It loads standard with windows 7.  Also the ssd toolbox still finds my ssd drive and runs on it.

                • 5. Re: Weird SSD Benchmark
                  Einride

                  The result depicted in your benchmark is not weird--it is common for "physical disk" read tests on SSDs. A physical disk test does not use the file system at all, and can be run on formatted or unformatted disks with or without partitions or operating systems, or with a mix of them.  In your case, I can tell from the shape of the test results that you have an operating system installed at the logical beginning of the SSD, that it is either Win Vista or Win7. and that you have probably run some file system read-write tests.

                   

                  A physical disk test uses "absolute sector" addressing to talk to the disk.  A typical data point will be generated by instructing the disk controller to read and return the data from sector number 1000 through sector number 1999.  The test program will time the transfer, and divide the total number of bits by the total number of seconds for the operation to complete, in order to produce a single data point--then move on to, say, sector number 10,000 and repeat.  It does not matter whether there is data in the test area, whether a sector may be part of a file, or whether a sector may be in a block of data on an SSD that has been marked "unavailable"--it all gets tested on an absolute sector read request.  By contrast, on a file system test, all of this matters.

                   

                  I am glad you posted on this point, because I am hoping that someone can answer my question--Why is the data transfer rate (read, not write) for an SSD slowed down so seriously in areas when there is actual data on the disk?  And, the folllow-up question--Is any of the testing we have been doing on SSDs with test programs representative of the performance during actual usage?

                   

                  I get physical disk test results very similar to yours using HD Tune and SiSoft Sandra.  Here is a series of tests from Sandra over a period of one month.

                   

                  Comparison of Physical Disk results.png

                  Sandra provides a large database of test results from a wide variety of hardware and systems.  Sandra also keeps your own prior results in the same database, and can display results from a current test, as well as your choice of four other results from the database.  Sandra uses a small number of data points for the physical disk test compared to other test programs, and an unadjustable test block size of 10MB, so some of the finer detail is not there.   Here is what the five traces represent.

                   

                  The blue trace is for a Samsung disk and not relevant here--except for its odd shape.  All of the other traces were from one Intel SSD as described in the window title.

                   

                  The purple trace was taken when the disk had been in use a few days and the Win7 system was using the original driver for the drive controller.  The remaining traces were taken using an RST driver. The large dip on the left is where the OS is installed.  The first three or more % was the location of the hibernate file, which was never used, and that area tests high.  The OS area tests low.  There is a low dip in the center of the test--this is where Sandra places its test file for a file system test, and several of these tests had been run prior to generating the purple trace.  There is a low dip at about the 20% mark which, I believe is the area used for AS SSD tests as well as for HD Tune's file system tests.

                   

                  The green, gold, and red traces were taken using an RST driver.  Note that the high results on these traces never get as high as the purple trace.  The green trace was taken after the gold trace, and after quite a bit more testing with HD Tune.

                   

                  Finally, the red trace was taken after I got curious about the SSD Toolbox, and ran its (extended, thorough, complete?) read-write diagnostic test on the disk.  Note that essentially all of the flat-topped high-performance areas of the other traces are missing from the red trace, and it appears that read performance has been knocked down significantly in every area where data has been written.  The Toolbox diagnostic test writes data into every free (by the file system) area of a disk and then reads the data back, and then apparently leaves the data there, but with no references to it in the master file table.

                   

                  My point here is that the Intel SSDs test out at about the Intel spec for read performance only in places where there is no data on the disk.  And in the data areas the performance is significantly lower.  On jznomoney's test, you can see the read rate dip from 240 MB/sec to as low as 140 MB/sec in the data areas.  On my less detailed tests the results are similar.

                   

                  So, any comments on the significance of all this?

                  • 6. Re: Weird SSD Benchmark
                    ambizytl

                    Not using the msahci driver means you have to run the optimizer for TRIM to work, which you can do either manually or via scheduling. I showed you my test result that is consistent with what I always get using AS SSD.

                    • 7. Re: Weird SSD Benchmark
                      ambizytl

                      How do you know you are running in AHCI? Looking at your picture, I see amdsata and no indication of AHCI.

                      • 8. Re: Weird SSD Benchmark
                        jznomoney

                        ok well I changed the the default microsoft driver now here's my result.

                        as-ssd-bench INTEL SSDSA2M160 2.14.2010 10-59-12 PM.png

                        • 9. Re: Weird SSD Benchmark
                          ambizytl

                          Run the Optimizer from SSD Toolbox and see if that makes a difference.

                           

                          I see the figure under msahci changed--I don't have that figure using my version of AS SSD. How much space is left on your SSD?

                          • 10. Re: Weird SSD Benchmark
                            ambizytl

                            Here is another test I ran a few minutes ago using AS SSD:

                             

                            as-ssd-bench INTEL SSDSA2M160 2.15.2010 8-23-18 AM.png

                            • 11. Re: Weird SSD Benchmark
                              Einride

                              It is puzzling that the info displayed in the upper left box in AS SSD is shifting around for the various posts above.

                               

                              In particular, the green text for the last post "64 K - OK".  I believe this is supposed to represent the free space on the disk.  A bizarre result.

                              • 12. Re: Weird SSD Benchmark
                                ambizytl

                                That is why I asked him how much space is left on his SSD.

                                 

                                I don't know how he changed from amdsata to msahci driver and if he truly is in AHCI mode.

                                • 13. Re: Weird SSD Benchmark
                                  jznomoney

                                  my drive has 2 partitions, a windows, and a games.  I had deleted that stupid windows 100mb boot patition, recreated the first partition.  Then I had reinstalled Windows 7 and reran the test with the default microsoft AHCI driver.

                                  ahci.png

                                  • 14. Re: Weird SSD Benchmark
                                    ambizytl

                                    That looks odd to me, seeing duplicates and quadruplicates listed.

                                    1 2 Previous Next