Re: Bad performance when reads and writes on same LUN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2011-09-02 21:24, Neto, Antonio Jose Rodrigues wrote:
> Thanks Jens, but why when we run READS only (not mixed) we don't have performance issues? (We run with direct=0)?

Let me repeat: please don't top post! Etiquette on most open source
lists are to bottom post, like you can see other people are doind.

Apparently you don't have performance problems with buffered reads since
you don't need a large queue depth to get good performance on reads
alone.

Since you seem a little lost, let me suggest that you start by
diagnosing the raw read vs write performance of the device. Get rid of
the file system, use filename=/dev/XXX directly to access that device.
Beware that it will eat the data that is currently on the device. Once
you get an idea for what the device can actually do, then you can start
to consider what impact the file system has on that (if any, I looked at
your job file, and each job would use separate files. so you should not
have any buffered vs direct unhappiness going on).


-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux