I just realised there was already some effort in 2010 to have per-xl
latency measurement.
See commit d90c2f86ca7a8f6660e98da1e48c4798539b7d51.
Turns out you need to send SIGUSR2 to the process to enable it.
And the stats are collected through statedump.
Haven't yet tested it. Will try and get
On Tue, May 30, 2017 at 6:42 PM, Shyam wrote:
> On 05/30/2017 05:28 AM, Krutika Dhananjay wrote:
>
>> You're right. With brick graphs, this will be a problem.
>>
>> Couple of options:
>>
>> 1. To begin with we identify points where we think it would be useful to
>> load
On 05/30/2017 05:28 AM, Krutika Dhananjay wrote:
You're right. With brick graphs, this will be a problem.
Couple of options:
1. To begin with we identify points where we think it would be useful to
load io-stats in the brick graph and unconditionally have
glusterd-volgen load them in the
You're right. With brick graphs, this will be a problem.
Couple of options:
1. To begin with we identify points where we think it would be useful to
load io-stats in the brick graph and unconditionally have glusterd-volgen
load them in the volfile only at these places (not very useful if we want
On 05/26/2017 05:44 AM, Krutika Dhananjay wrote:
Hi,
debug/io-stats and debug/trace are immensely useful for isolating
translators that are performance bottlenecks and those that are causing
iatt inconsistencies, respectively.
There are other translators too under xlators/debug such as
On Fri, May 26, 2017 at 3:14 PM, Krutika Dhananjay
wrote:
> Hi,
>
> debug/io-stats and debug/trace are immensely useful for isolating
> translators that are performance bottlenecks and those that are causing
> iatt inconsistencies, respectively.
>
> There are other