Announcement

Collapse
No announcement yet.

QED: A New, High Performance QEMU Disk Format

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • QED: A New, High Performance QEMU Disk Format

    Phoronix: QED: A New, High Performance QEMU Disk Format

    Linux-KVM mentions QED, the new QEMU Enhanced Disk format. This new disk format for QEMU/KVM is designed to be much faster than QCOW2 and other existing disk formats available to virtualization users...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    It should be interesting to benchmark qed against qcow and raw.

    - Gilboa
    oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
    oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
    oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
    Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

    Comment


    • #3
      Isn't raw access to a real disk always faster?

      Comment


      • #4
        Originally posted by Chewi View Post
        Isn't raw access to a real disk always faster?
        Does RAW provide access to TRIM?

        Comment


        • #5
          Originally posted by Shining Arcanine View Post
          Does RAW provide access to TRIM?
          I think that's irrelevant if you're using a real disk.

          Comment


          • #6
            trim support doesn't necessarily require non-raw file system.
            Actually, I'm far from being an expert in this field, but I would imagine that implementing virtualized hardware w/ trim support is somewhat easier on raw-FS-partition, as qemu can simply pass the trim request (w/ address translation) from the guest to the underlying hardware.

            ... but as I as I said, I'm guessing

            As for performance, I would guess that raw will have the upper hand given the same optimization on the qemu side (E.g. write combination, etc). But given the fact that most of the effort is spent on optimizing advanced image types (qcow, etc), it's entirely possible that raw will not win the benchmark(s).

            - Gilboa
            oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
            oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
            oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
            Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

            Comment

            Working...
            X