Throughput is a function of block size & chunk size. For operations such as copying large files, then larger block/chunk sizes mean
higher throughput .. at the COST of I/Os per second.
There is no free lunch. Before doing any tuning, ask yourself what the normal mix of random, sequential, read, write, large and small
block I/O is. If you are constantly moving large files around, then by all means redo the RAID and file system setup, but if this exercise is an exception, then you may be better off leaving things as they are.
________________________________________
From: linux-raid-owner@vger.kernel.org [linux-raid-owner@vger.kernel.org] On Behalf Of Michal Soltys [soltys@ziu.info]
Sent: Thursday, November 18, 2010 2:43 PM
To: Zoltan Szecsei
Cc: linux-raid@vger.kernel.org
Subject: Re: Array read 3 time slower to read after data fully loaded
On 10-11-18 06:30, Zoltan Szecsei wrote:
Is the situation with reading into /dev/null instead of /home the same ?
As this is reading issue, one thing that came to my mind:
- make sure the kernel is _not_ compiled with CONFIG_MULTICORE_RAID456.
It's afaik still experimental and can cause severe slowdowns
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html