On 2018-10-05 20:34, Duncan wrote:
Wilson, Ellis posted on Fri, 05 Oct 2018 15:29:52 + as excerpted:
Is there any tuning in BTRFS that limits the number of outstanding reads
at a time to a small single-digit number, or something else that could
be behind small queue depths? I can't
Wilson, Ellis posted on Fri, 05 Oct 2018 15:29:52 + as excerpted:
> Is there any tuning in BTRFS that limits the number of outstanding reads
> at a time to a small single-digit number, or something else that could
> be behind small queue depths? I can't otherwise imagine what the
>
On 10/05/2018 06:40 AM, Duncan wrote:
> Wilson, Ellis posted on Thu, 04 Oct 2018 21:33:29 + as excerpted:
>
>> Hi all,
>>
>> I'm attempting to understand a roughly 30% degradation in BTRFS RAID0
>> for large read I/Os across six disks compared with ext4 atop mdadm
>> RAID0.
>>
>>
Wilson, Ellis posted on Thu, 04 Oct 2018 21:33:29 + as excerpted:
> Hi all,
>
> I'm attempting to understand a roughly 30% degradation in BTRFS RAID0
> for large read I/Os across six disks compared with ext4 atop mdadm
> RAID0.
>
> Specifically, I achieve performance parity with BTRFS in
On 5.10.2018 00:33, Wilson, Ellis wrote:
> Hi all,
>
> I'm attempting to understand a roughly 30% degradation in BTRFS RAID0
> for large read I/Os across six disks compared with ext4 atop mdadm RAID0.
>
> Specifically, I achieve performance parity with BTRFS in terms of
> single-threaded
Hi all,
I'm attempting to understand a roughly 30% degradation in BTRFS RAID0
for large read I/Os across six disks compared with ext4 atop mdadm RAID0.
Specifically, I achieve performance parity with BTRFS in terms of
single-threaded write and read, and multi-threaded write, but poor
