qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] QCOW2 deduplication key value store
Date: Wed, 27 Mar 2013 14:20:18 +0100	[thread overview]
Message-ID: <20130327132018.GA4095@irqsave.net> (raw)


Hello,

I am starting this thread so we can discuss of the choice of a good key/value
store for the QCOW2 deduplication.

One of the main goal is to keep the ratio between the number of cluster written
and the number of dedup metadata io high.

I initially though about taking the first two stages of SILT
(http://goo.gl/x7UcI) to build the key value store.

The very nice thing about the two first stage of SILT is that the write io
involved are not random at all: The log is obviously not random and the
conversion into the second stage hash table can be done sequentially.
This makes the io ratio very high.

Kevin later thought about combining the first stage of SILT with a big hash
table as a second stage.
While this method is simpler I don't understand how we can inject the first
stage into this big table without generating a log of random ios.

Best regards

Benoît

                 reply	other threads:[~2013-03-27 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130327132018.GA4095@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).