LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  June 2019

XROOTD-L June 2019

Subject:

Re: cms.perf script - how to contribute

From:

Adrian Sevcenco <[log in to unmask]>

Reply-To:

Support use of xrootd by HEP experiments <[log in to unmask]>

Date:

Wed, 19 Jun 2019 00:48:24 +0300

Content-Type:

multipart/signed

Parts/Attachments:

Parts/Attachments

text/plain (90 lines) , smime.p7s (90 lines)

On 6/19/19 12:03 AM, Andrew Hanushevsky wrote:
> Hi Adrian,
> 
> -----Original Message----- From: Adrian Sevcenco
> Sent: Tuesday, June 18, 2019 9:35 AM
> To: [log in to unmask]
> Subject: cms.perf script - how to contribute
> 
> Hi! With the help of Oliver Freyermuth i rewrote the script
> /usr/share/xrootd/utils/XrdOlbMonPerf
> which in documentation is referenced as cms_MonPerf
> http://xrootd.org/doc/dev410/cms_config.htm#_Toc8247264
> 
> in the form that can be seen here:
> https://github.com/adriansev/bin-scripts/blob/master/cms_monPerf
> 
> w.r.t to old script i would have some questions :
> 1. what would be the proper name to have
> +++So, cms_MonPerf is your preferred name. That's fine. I will simply 
> stop documenting the old name.
actually in documentation the name is cms_MonPerf :)
this is why i asked what name should have :)

> 2. i seen that both cms.perf and the script have some timing arguments
> moreover the ols script is supposed to run in the loop ...
> what is the relation between cms.pref int parameter and the "interval"
> argument that the script is supposed to have?
> +++Yes, the script needs to run in a loop and produce output at the 
> frequency you specify as a parameter to the script. The int parameter is 
> simply the estimated time between the program reporting something. The 
> "int" value should be somewhat larger that the actual reporting time 
> that you would specify as a parameter to the script. The reason is that 
> the server uses the int value to determine if the reporting program is 
> dead (i.e. not reporting) and needs to be restarted. Yes, I agree, none 
> of that is explained in the doc.
ok, i see .. the default is 1s and then the script takes 1s for cpu util 
determination and 1s for each valid network interface for each have to 
measure the instantaneous bandwidth

> 3. is it really relevant for memory load to take into account the
> buffers and cache?
> +++No, not at all. I don't even think Linux takes that into account.
the linux kernel fills as much is possible the not commited memory with 
buffers and cache and then if the pressure from to allocator increase, 
it release the buffers and caches
so, it would be ok to change to compute the memory load based only on:
(MemTotal - MemAvailable)*100/MemTotal  ?
http://man7.org/linux/man-pages/man5/proc.5.html /proc/meminfo

> i assumed that :
> 1. -m <shmkey> option is something too old to be cared about
> +++Correct. Forget about it.
great

> 2. -n netspeed have no meaning because either it is know directly
> or, for virtio interfaces, even the human admin cannot determine it
> (so for virtio interfaces the net load will be always 0)
> As a generic network load measurement, packets per second averaged over 
> the reporting interval (which can be computed) is a good indicator of 
> how busy the interface is. I'd suggest simply doing that.
"the rules" of the script says that the value should be normalized to 
some 100% ... with packets i cannot do this because : 1. they have 
variable size; 2. i have no speed in pkt/s for the network interface

> 3. -I netintf this was also skipped as the net load will be taken as the
> maximum of all physical up interfaces, with the assumption that on the
> xrootd data server at least 1 interface is dedicated to xrootd server
> and that is the most utilized.
> +++Probably good enough here for the general cose.
ok

> the script make use only of awk and assumes linux.
> +++That's fine. At least it will work virtually all Linux distros. 
> Thanks a heap -- both of you!
> 
> As for getting it into the repo, simply create a pull request and I will 
> merge it in.
great!

Thanks a lot!
Adrian


########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use