From: Jens Axboe <axboe@kernel.dk>
To: Yufei Ren <yufei.ren@stonybrook.edu>
Cc: fio@vger.kernel.org
Subject: Re: Why zipf distribution can not be 1.0
Date: Mon, 28 Jan 2013 09:06:35 +0100 [thread overview]
Message-ID: <20130128080635.GR15635@kernel.dk> (raw)
In-Reply-To: <CAG5pYQcNzX7LJQeLJCZWK1TRYYQOy5Wy_peKHSoC2OXCiBbYcw@mail.gmail.com>
On Sun, Jan 27 2013, Yufei Ren wrote:
> Hi,
>
> Is the 'zipf theta' the value of the exponent characterizing the zipf
> distribution? If so, why could not it be 1.0? With the following job
> file, fio sent out an error - fio: zipf theta must different than 1.0.
>
> [job]
> ioengine=null
> rw=randread
> norandommap
> size=1280m
> bs=4k
> random_distribution=zipf:1
>
> I looked through the fio zipf library but was confused with
> zipf_next() function? Any illustration about this zipf distribution
> generator?
The point is that a theta of 1.0 would be the same as a normal uniform
distrobution. But perhaps it should just be allowed, you should get what
you ask for...
Not sure on your last question. Can you expand on that? If it's on the
zipf distribution in general, google/wikipedia is your friend :-)
--
Jens Axboe
prev parent reply other threads:[~2013-01-28 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 19:43 Why zipf distribution can not be 1.0 Yufei Ren
2013-01-28 8:06 ` Jens Axboe [this message]
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=20130128080635.GR15635@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=yufei.ren@stonybrook.edu \
/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