On 2014-09-30 03:17, Andrey Kuzmin wrote:
On Tue, Sep 30, 2014 at 1:14 PM, Jon Tango <[email protected]> wrote:
The same thing could be done by partitioning the SSD in the operating system
with the desired partition size, and then running a time-based fio job against
the partition.
Basically, fio options offset/size should yield the same net result, but I'm
always unsure on what is the actual effect of mixing size and time_based in a
single job, and whether fio will wrap around the specified size to the
specified offset if the job is time-based. HOWTO could have used some
clarification on size/time_based interaction.
Regards,
Andrey
On Sep 30, 2014 11:41 AM, "Sitsofe Wheeler" <[email protected]> wrote:
On 30 September 2014 07:34, Jon Tango <[email protected]> wrote:
The taskfile is this:
I should have been more specific - you need to show both the _vdbench_
parameter file that you are comparing to in addition to showing your
fio job file.
--
Sitsofe |http://sucs.org/~sits/
--
To unsubscribe from this list: send the line "unsubscribe fio" in the
body of a message [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe fio" in the body of a
message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
I'm really wanting to avoid the filesystem, they create so much interference. I
am focusing on just testing the raw device :)
I'm not sure why a filesystem should be involved in partitioning, that
happens at the raw device level.
I think there's some limitation in Windows that doesn't allow partition
raw IO. I may be mistaken.
But I agree, partition would work. But just limiting the LBA range with
size= will do the same job.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
