Here are the results of the last run:
https://docs.google.com/spreadsheets/d/19JqvuFKZxKifgrhLF-5-bgemYj8XKldUox1QwsmGj2k/edit?usp=sharing
Each test has been run with a rough approximation of the best configuration
I've found (in number of client and brick threads), but I haven't done an
On Tue, Feb 5, 2019 at 10:57 PM Xavi Hernandez
wrote:
> On Wed, Feb 6, 2019 at 7:00 AM Poornima Gurusiddaiah
> wrote:
>
>>
>>
>> On Tue, Feb 5, 2019, 10:53 PM Xavi Hernandez > wrote:
>>
>>> On Fri, Feb 1, 2019 at 1:51 PM Xavi Hernandez
>>> wrote:
>>>
On Fri, Feb 1, 2019 at 1:25 PM
Thank You for all the detailed explanation. If its the disk saturating, if
we run some of the above mentioned tests(with multithreads) on plain xfs,
we should hit the saturation right. Will try out some tests, this is
interesting.
Thanks,
Poornima
On Wed, Feb 6, 2019 at 12:27 PM Xavi Hernandez
On Wed, Feb 6, 2019 at 7:00 AM Poornima Gurusiddaiah
wrote:
>
>
> On Tue, Feb 5, 2019, 10:53 PM Xavi Hernandez
>> On Fri, Feb 1, 2019 at 1:51 PM Xavi Hernandez
>> wrote:
>>
>>> On Fri, Feb 1, 2019 at 1:25 PM Poornima Gurusiddaiah <
>>> pguru...@redhat.com> wrote:
>>>
Can the threads be
On Tue, Feb 5, 2019, 10:53 PM Xavi Hernandez On Fri, Feb 1, 2019 at 1:51 PM Xavi Hernandez
> wrote:
>
>> On Fri, Feb 1, 2019 at 1:25 PM Poornima Gurusiddaiah
>> wrote:
>>
>>> Can the threads be categorised to do certain kinds of fops?
>>>
>>
>> Could be, but creating multiple thread groups for
On Fri, Feb 1, 2019 at 1:51 PM Xavi Hernandez wrote:
> On Fri, Feb 1, 2019 at 1:25 PM Poornima Gurusiddaiah
> wrote:
>
>> Can the threads be categorised to do certain kinds of fops?
>>
>
> Could be, but creating multiple thread groups for different tasks is
> generally bad because many times
On Fri, Feb 1, 2019 at 1:25 PM Poornima Gurusiddaiah
wrote:
> Can the threads be categorised to do certain kinds of fops?
>
Could be, but creating multiple thread groups for different tasks is
generally bad because many times you end up with lots of idle threads which
waste resources and could
Can the threads be categorised to do certain kinds of fops? Read/write
affinitise to certain set of threads, the other metadata fops to other set
of threads. So we limit the read/write threads and not the metadata
threads? Also if aio is enabled in the backend the threads will not be
blocked on
On Thu, Jan 31, 2019 at 10:53:48PM -0800, Vijay Bellur wrote:
> Perhaps we could throttle both aspects - number of I/O requests per disk
While there it would be nice to detect and report a disk with lower than
peer performance: that happen sometimes when a disk is dying, and last
time I was hit
On Thu, Jan 31, 2019 at 11:12 PM Xavi Hernandez
wrote:
> On Fri, Feb 1, 2019 at 7:54 AM Vijay Bellur wrote:
>
>>
>>
>> On Thu, Jan 31, 2019 at 10:01 AM Xavi Hernandez
>> wrote:
>>
>>> Hi,
>>>
>>> I've been doing some tests with the global thread pool [1], and I've
>>> observed one important
On Fri, Feb 1, 2019 at 7:54 AM Vijay Bellur wrote:
>
>
> On Thu, Jan 31, 2019 at 10:01 AM Xavi Hernandez
> wrote:
>
>> Hi,
>>
>> I've been doing some tests with the global thread pool [1], and I've
>> observed one important thing:
>>
>> Since this new thread pool has very low contention
On Thu, Jan 31, 2019 at 10:01 AM Xavi Hernandez
wrote:
> Hi,
>
> I've been doing some tests with the global thread pool [1], and I've
> observed one important thing:
>
> Since this new thread pool has very low contention (apparently), it
> exposes other problems when the number of threads grows.
Hi,
I've been doing some tests with the global thread pool [1], and I've
observed one important thing:
Since this new thread pool has very low contention (apparently), it exposes
other problems when the number of threads grows. What I've seen is that
some workloads use all available threads on
13 matches
Mail list logo
