JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


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

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  2005

LCG-ROLLOUT 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: TotalCPU count on the GOC Mon

From:

Steve Traylen <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Fri, 28 Jan 2005 17:30:21 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (147 lines)

On Fri, Jan 28, 2005 at 05:06:48PM -0000 or thereabouts, pierre girard wrote:
> Hi Min,
>
> Unfortunately, this CPU count strategy does not work with CCIN2P3-LCG2
> site.

I don't think it really matters to the system that the CPU count is wrong.
It might matter for to publicity of course but so long as the
ETT time goes up when you start queuing jobs then things will
be reasnoable.

 Steve
>
> Indeed, the real number of physical CPUs supplied to the grid at CC is
> 100 CPUs at this moment, and more than 700 CPUs very soon (hopefully
> next week).
>
> With our batch system, we define in general 2 queues by physical CPU,
> but each "queue" (called a WorkPoint) can be configured to accept
> several classes of jobs (something like short (A), medium (G) and long
> (T)).
>
> At this moment, the Glue schema does not allow us to express the subtely
> of our batch system queue mechanism. As a consequence, it is impossible
> for you to infer the total of real CPUs from the published data. What we
> currently publishes are virtual CPUs instead of real CPUs.
>
> The solution consisting in adding CPU counts at Subcluster level,
> proposed by stephen, should be the solution to our problem.
>
> Anyway, in our specific and current case, the solution is to take the
> max of the queues.
>
> But a solution could be to sum systematically the CPUs of each queue by
> site. Indeed, this value has the same meaning for all the sites.
> According to me, it reflects the number of jobs a site pretends to be
> able to perform simultaneously, what I call the virtual CPUs. It is the
> role of the site administrator to set correctly this value in
> concordance with the real capacities of his/her site.
>
> When we will have the possibility to get the real CPU count, it will be
> very interesting to compute the ratio between virtual CPUs and real ones.
>
> Hope this helps ;).
>
> Pierre
>
>
>
>
>
>
> Min Tsai a écrit :
>
> >Hi All,
> >
> >The fix is in for the CPU count.  Three other sites had their CPU stats
> >change: CCIN2P3-LCG2, INFN-LNL-LCG, INFN-PADOVA.  Let me know if these
> >number are inaccurate for some reason.
> >
> >Best Regards,
> >Min
> >
> >-----Original Message-----
> >From: LHC Computer Grid - Rollout [mailto:[log in to unmask]] On
> >Behalf Of Min Tsai
> >Sent: Wednesday, January 26, 2005 12:41 PM
> >To: [log in to unmask]
> >Subject: Re: [LCG-ROLLOUT] TotalCPU count on the GOC Mon
> >
> >Dear Anar,
> >
> >Typically CPU stats for queues on a single CE repeat all refer to the same
> >set of CPUs.  So to prevent recount of CPU Gstat adds up the CPU stats for
> >the first queue it encounters for each unique CE.  So in your case:
> >
> >It adds up:
> >GlueCEUniqueID=lcg03.gsi.de:2119\/jobmanager-torque-alice  2 CPU
> >GlueCEUniqueID=lcg06.gsi.de:2119\/jobmanager-lcglsf-alice  16 CPU
> >
> >I have not noticed a configuration like yours before, so I will make a
> >modification by adding CPU from queues that have different total CPU
> >statistics even though they reside on the same CE.  The only problem we will
> >have if when 2 queues on a single CE has the same total CPU count even
> >though they are referring to 2 completely different clusters.
> >
> >I hope this will correct the CPU problem for you site.  Thank you for
> >providing this feedback!  I will let you know once this I have tested and
> >complete this change.
> >
> >Cheers,
> >Min
> >
> >
> >
> >
> >
> >-----Original Message-----
> >From: LHC Computer Grid - Rollout [mailto:[log in to unmask]] On
> >Behalf Of Anar Manafov
> >Sent: Wednesday, January 26, 2005 11:59 AM
> >To: [log in to unmask]
> >Subject: [LCG-ROLLOUT] TotalCPU count on the GOC Mon
> >
> >Good day to ALL!
> >
> >I have mentioned that on the monitoring (http://goc.grid.sinica.edu.tw/
> >gstat/lcg03.gsi.de/) we (GSI) publishing only 18 CPU (Total CPU). So, I
> >wonder how this number is calculated and why not all of the queues are
> >affected.
> >We have 2 different CE:
> >Torque CE (with 2 CPU).
> >LSF CE (more than 300 CPU),
> >in LSF we have &#8220;dteam&#8221; and &#8220;alice&#8221; queues.
> >For &#8220;alice&#8221; ~ 16 PCU
> >For &#8220;dteam&#8221;  ~ 344 CPU or something (Later on, when we finish
> >the test of
> >our new pool-accounts algorithm we will publish more CPU on the
> >&#8220;alice&#8221;).
> >
> >So, my question would be which algorithm monitoring uses to calculate Total
> >CPU amount?
> >
> >I would appreciate any comment on this.
> >
> >Thank you very much in advance.
> >
> >Best of luck,
> >
> >Anar
> >
> >
> >
>
> --
> ______________________
> Pierre GIRARD
> Grid Computing Team Member
> IN2P3/CNRS Computing Centre - Lyon (FRANCE)
> http://cc.in2p3.fr
> Tel. +33 4.78.93.08.80 | Fax. +33 4.72.69.41.70 | e-mail: [log in to unmask]

--
Steve Traylen
[log in to unmask]
http://www.gridpp.ac.uk/

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
November 2023
June 2023
May 2023
April 2023
March 2023
February 2023
September 2022
June 2022
May 2022
April 2022
February 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
February 2021
January 2021
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 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
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 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
November 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
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 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
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

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