Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
Joe,
BTW, Vipul (in CC) is also looking to quantify the impact of enabling
io-stats counters permanently.
It'd be great if you both could help each other out.
~kaushal
On Tue, Jul 22, 2014 at 12:54 PM, Pranith Kumar Karampuri
wrote:
>
> On 07/22/2014 12:07 PM, Kaushal M wrote:
>>
>> The clear you have at top (the one for "clear-stats") is for 'top
>> clear'. Below there is a section with GF_CLI_INFO_CLEAR, which handles
>> 'profile info clear'.
>
> Cool. Thanks :-). The stuff that is present on master for 'profile' is so
> much better :-)
>
> Pranith
>
>>
>> ~kaushal
>>
>> On Tue, Jul 22, 2014 at 11:50 AM, Pranith Kumar Karampuri
>> wrote:
>>>
>>> On 07/22/2014 11:43 AM, Kaushal M wrote:
'gluster volume profile info clear' should clear the stats as
well.
From 'gluster volume help'
volume profile {start|info [peek|incremental
[peek]|cumulative|clear]|stop} [nfs]
>>>
>>> According to the code it is clearing only stats of 'top' not of the
>>> 'profile'
>>>
>>> Pranith
>>>
On Tue, Jul 22, 2014 at 11:39 AM, Joe Julian
wrote:
>
> On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote:
>>
>>
>> On 07/18/2014 03:05 AM, Joe Julian wrote:
>>>
>>> What impact, if any, does starting profiling (gluster volume profile
>>> $vol
>>> start) have on performance?
>>
>> Joe,
>> According to the code the only extra things it does is calling
>> gettimeofday() call at the beginning and end of the FOP to calculate
>> latency, increment some variables. So I guess not much?
>>
> So far so good. Is the only way to clear the stats to restart the
> brick?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
>>>
>>>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/22/2014 12:07 PM, Kaushal M wrote:
The clear you have at top (the one for "clear-stats") is for 'top
clear'. Below there is a section with GF_CLI_INFO_CLEAR, which handles
'profile info clear'.
Cool. Thanks :-). The stuff that is present on master for 'profile' is
so much better :-)
Pranith
~kaushal
On Tue, Jul 22, 2014 at 11:50 AM, Pranith Kumar Karampuri
wrote:
On 07/22/2014 11:43 AM, Kaushal M wrote:
'gluster volume profile info clear' should clear the stats as
well.
From 'gluster volume help'
volume profile {start|info [peek|incremental
[peek]|cumulative|clear]|stop} [nfs]
According to the code it is clearing only stats of 'top' not of the
'profile'
Pranith
On Tue, Jul 22, 2014 at 11:39 AM, Joe Julian wrote:
On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote:
On 07/18/2014 03:05 AM, Joe Julian wrote:
What impact, if any, does starting profiling (gluster volume profile
$vol
start) have on performance?
Joe,
According to the code the only extra things it does is calling
gettimeofday() call at the beginning and end of the FOP to calculate
latency, increment some variables. So I guess not much?
So far so good. Is the only way to clear the stats to restart the brick?
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
The clear you have at top (the one for "clear-stats") is for 'top
clear'. Below there is a section with GF_CLI_INFO_CLEAR, which handles
'profile info clear'.
~kaushal
On Tue, Jul 22, 2014 at 11:50 AM, Pranith Kumar Karampuri
wrote:
>
> On 07/22/2014 11:43 AM, Kaushal M wrote:
>>
>> 'gluster volume profile info clear' should clear the stats as
>> well.
>>
>> From 'gluster volume help'
>>volume profile {start|info [peek|incremental
>> [peek]|cumulative|clear]|stop} [nfs]
>
> According to the code it is clearing only stats of 'top' not of the
> 'profile'
>
> Pranith
>
>>
>> On Tue, Jul 22, 2014 at 11:39 AM, Joe Julian wrote:
>>>
>>> On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote:
On 07/18/2014 03:05 AM, Joe Julian wrote:
>
> What impact, if any, does starting profiling (gluster volume profile
> $vol
> start) have on performance?
Joe,
According to the code the only extra things it does is calling
gettimeofday() call at the beginning and end of the FOP to calculate
latency, increment some variables. So I guess not much?
>>> So far so good. Is the only way to clear the stats to restart the brick?
>>>
>>> ___
>>> Gluster-devel mailing list
>>> Gluster-devel@gluster.org
>>> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/22/2014 11:56 AM, Joe Julian wrote: On 07/21/2014 11:20 PM, Pranith Kumar Karampuri wrote: On 07/22/2014 11:39 AM, Joe Julian wrote: On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote: On 07/18/2014 03:05 AM, Joe Julian wrote: What impact, if any, does starting profiling (gluster volume profile $vol start) have on performance? Joe, According to the code the only extra things it does is calling gettimeofday() call at the beginning and end of the FOP to calculate latency, increment some variables. So I guess not much? So far so good. Is the only way to clear the stats to restart the brick? I think when the feature is initially proposed we wanted two things 1) cumulative stats 2) Interval stats Interval stats get cleared whenever 'gluster volume profile info' is executed (Although it starts counting the next set of fops that happen after this command execution). But there is no way to clear the cumulative stats. It would be nice if you could give some feedback about what you liked/what you think should change to make better use of it. So I am guessing there wasn't big performance hit? Pranith No noticeable performance hit, no. I'm writing a whitepaper for the best practices for OpenStack on GlusterFS so I needed some idea how qemu actually uses the filesystem. What the operations are so I can look at not only the best ways to tune for that use, but how to build the systems around that. At this point, I'm just collecting data. TBH, I hadn't noticed the interval data. That should be perfect for this. I'll poll it in XML and run the numbers in a few days. Joe, Do let us know your feedback. It needs some real-world usage suggestions from users like you :-). Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/21/2014 11:20 PM, Pranith Kumar Karampuri wrote: On 07/22/2014 11:39 AM, Joe Julian wrote: On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote: On 07/18/2014 03:05 AM, Joe Julian wrote: What impact, if any, does starting profiling (gluster volume profile $vol start) have on performance? Joe, According to the code the only extra things it does is calling gettimeofday() call at the beginning and end of the FOP to calculate latency, increment some variables. So I guess not much? So far so good. Is the only way to clear the stats to restart the brick? I think when the feature is initially proposed we wanted two things 1) cumulative stats 2) Interval stats Interval stats get cleared whenever 'gluster volume profile info' is executed (Although it starts counting the next set of fops that happen after this command execution). But there is no way to clear the cumulative stats. It would be nice if you could give some feedback about what you liked/what you think should change to make better use of it. So I am guessing there wasn't big performance hit? Pranith No noticeable performance hit, no. I'm writing a whitepaper for the best practices for OpenStack on GlusterFS so I needed some idea how qemu actually uses the filesystem. What the operations are so I can look at not only the best ways to tune for that use, but how to build the systems around that. At this point, I'm just collecting data. TBH, I hadn't noticed the interval data. That should be perfect for this. I'll poll it in XML and run the numbers in a few days. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/22/2014 11:43 AM, Kaushal M wrote:
'gluster volume profile info clear' should clear the stats as well.
From 'gluster volume help'
volume profile {start|info [peek|incremental
[peek]|cumulative|clear]|stop} [nfs]
According to the code it is clearing only stats of 'top' not of the
'profile'
Pranith
On Tue, Jul 22, 2014 at 11:39 AM, Joe Julian wrote:
On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote:
On 07/18/2014 03:05 AM, Joe Julian wrote:
What impact, if any, does starting profiling (gluster volume profile $vol
start) have on performance?
Joe,
According to the code the only extra things it does is calling
gettimeofday() call at the beginning and end of the FOP to calculate
latency, increment some variables. So I guess not much?
So far so good. Is the only way to clear the stats to restart the brick?
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On Tue, Jul 22, 2014 at 11:39 AM, Joe Julian wrote:
On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote:
On 07/18/2014 03:05 AM, Joe Julian wrote:
What impact, if any, does starting profiling (gluster volume profile $vol
start) have on performance?
Joe,
According to the code the only extra things it does is calling
gettimeofday() call at the beginning and end of the FOP to calculate
latency, increment some variables. So I guess not much?
So far so good. Is the only way to clear the stats to restart the brick?
On 07/21/2014 11:13 PM, Kaushal M wrote:
'gluster volume profile info clear' should clear the stats as well.
From 'gluster volume help'
volume profile {start|info [peek|incremental
[peek]|cumulative|clear]|stop} [nfs]
So only on 3.5. We're running 3.4.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/22/2014 11:39 AM, Joe Julian wrote: On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote: On 07/18/2014 03:05 AM, Joe Julian wrote: What impact, if any, does starting profiling (gluster volume profile $vol start) have on performance? Joe, According to the code the only extra things it does is calling gettimeofday() call at the beginning and end of the FOP to calculate latency, increment some variables. So I guess not much? So far so good. Is the only way to clear the stats to restart the brick? I think when the feature is initially proposed we wanted two things 1) cumulative stats 2) Interval stats Interval stats get cleared whenever 'gluster volume profile info' is executed (Although it starts counting the next set of fops that happen after this command execution). But there is no way to clear the cumulative stats. It would be nice if you could give some feedback about what you liked/what you think should change to make better use of it. So I am guessing there wasn't big performance hit? Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
'gluster volume profile info clear' should clear the stats as well.
>From 'gluster volume help'
volume profile {start|info [peek|incremental
[peek]|cumulative|clear]|stop} [nfs]
On Tue, Jul 22, 2014 at 11:39 AM, Joe Julian wrote:
>
> On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote:
>>
>>
>> On 07/18/2014 03:05 AM, Joe Julian wrote:
>>>
>>> What impact, if any, does starting profiling (gluster volume profile $vol
>>> start) have on performance?
>>
>> Joe,
>> According to the code the only extra things it does is calling
>> gettimeofday() call at the beginning and end of the FOP to calculate
>> latency, increment some variables. So I guess not much?
>>
>
> So far so good. Is the only way to clear the stats to restart the brick?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/17/2014 07:30 PM, Pranith Kumar Karampuri wrote: On 07/18/2014 03:05 AM, Joe Julian wrote: What impact, if any, does starting profiling (gluster volume profile $vol start) have on performance? Joe, According to the code the only extra things it does is calling gettimeofday() call at the beginning and end of the FOP to calculate latency, increment some variables. So I guess not much? So far so good. Is the only way to clear the stats to restart the brick? ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] What's the impact of enabling the profiler?
On 07/18/2014 03:05 AM, Joe Julian wrote: What impact, if any, does starting profiling (gluster volume profile $vol start) have on performance? Joe, According to the code the only extra things it does is calling gettimeofday() call at the beginning and end of the FOP to calculate latency, increment some variables. So I guess not much? Pranith ___ Gluster-users mailing list gluster-us...@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
