Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-63

Study of the lustre performance with SFA10K

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • 10130

    Description

      Hi, I have been investigating the disk and lustre benchmark on SFA10K. Overall, the lustre performance on SFA is good. Getting 10GB/sec over the Lustre clients. However, I would have more reasonable benchmark procedures on the lustre.
      What I say mean, we usually run the following benchmark steps to make sure each device or layer are healthy.
      1. sgpdd-survey
      2. obdfilter-survey
      3. lnetself-test
      4. IOR/iozone

      Actually, we want to have a result which 1. sgp_dd-survey > 2. obdfilter-survey > 4.IOR/iozone due to each layer has small overhead. However, in my current testing, obdfilter-survey resutls are mostly faster than sgpdd-survey, or IOR/iozone results are better than obdfilter-survey in some configurations which does not make sense.

      So, I wonder if we could improve each survey or procedure to get maximum performance on each layer.

      I'm attaching the obdfilter-survey and sgpdd-survey results which I got on SFA10K.
      I only used 1 RAID processor on SFA and connects to a server with QDR which means maximum bandwidth between OSS and SFA10K is 3.2GB/sec.

      There are two questions at least.
      1. Why I can only get around 2.5GB/sec on sgpdd-suvey. (single thread number was good, 3GB/sec, but other are not good)
      2. Why read number on obdfilter-survey can't achieve 3GB/sec when number of objects are increased. Finally, it can get 3GB/sec, but need more thread to get 3GB/sec.

      Ihara

      Attachments

        Activity

          People

            niu Niu Yawei (Inactive)
            ihara Shuichi Ihara (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: