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  May 2005

XROOTD-L May 2005

Subject:

Re: xrdcp throughput in new 20050502-0000

From:

Fabrizio Furano <[log in to unmask]>

Date:

04 May 2005 11:23:47 +0000Wed, 04 May 2005 11:23:47 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (248 lines)

Hi Pete,

  yes, you are right. Those messages are regular kXR_ok, which, if the 
client is able to find a pending request for them, are treated as 
unsolicited responses.
  The client does that by using the data structures built upon 
XrdOucRash, which are supposed to give quite little overhead.

  Hence the debugging of that infrastructure is complete. Async 
responses (or messages treated that way) are internally dispatched to 
the entities which are interested in them, in a way which is concurrent, 
since it's triggered by the receiver thread in 
XrdClientPhysicalConnection. While this is in progress, the app is free 
to process, and should be even able to issue other requests.

  If some day an unsolicited response will come, I have "only" to write 
a handler for that.

  I had a mail exchange with Gerri, and now with Ulrich, from which it 
became clear to me how I have to modify the policy for requesting a big 
block in advance (without causing brutal processing overhead).
  Also, expecially under ROOT, there are some situations in which such a 
mechanism must be switched temporarily off.

  I will take care of this in these days, after my furious debugging 
sessions (not on XrdClient...).

Fabrizio


Peter Elmer wrote:
>   Hi Fabrizio,
> 
>   Ah, the responses from the server here are implemented effectively as 
> unsolicited responses? (Or at least the client is handling them that way,
> so at least some debugging of that infrastructure has now been done?)
> 
>   One small detail: could you add something to the debugging printout: 
> 
> 
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
> 
> 
> so that it prints also the kXR_async* code for the response received? (Staying
> at less than 80 characters, of course ;-)
> 
>                                    Pete
> 
> On Tue, May 03, 2005 at 02:17:47PM +0200, Ulrich Schwickerath wrote:
> 
>>Hi, Fabrizio,
>>
>>Sure. The numbers I just sent were NON-InfiniBand, it is the unchanged  code 
>>compiled without patch and run over GE ethernet (no IPoIB or any other fancy 
>>stuff involved). For InfiniBand the degradation of the performance is 
>>smaller.  Sorry for being unprecise here. 
>>
>>So, here is the ethernet output:
>>$time  bin/arch/xrdcp -np -DIDebugLevel 1 
>>root://iwrcgtest.fzk.de//tmp/testfile.dat /dev/null >& ethernet.log
>>
>>real    0m28.277s
>>user    0m1.400s
>>sys     0m0.290s
>>
>>gives:
>>Overriding 'DebugLevel' with value 1.  Final value: 1
>>050503 14:08:04 001 Xrd: main (C) 2004 SLAC INFN xrdcp 0.2 beta
>>050503 14:08:04 001 Xrd: Create (C) 2004 SLAC INFN XrdClient 0.3
>>050503 14:08:04 001 Xrd: XrdClientUrlSet List of servers to connect to is 
>>[iwrcgop028.fzk.de]
>>050503 14:08:04 001 Xrd: ShowUrls The converted URLs count is 1
>>050503 14:08:04 001 Xrd: ShowUrls URL n.1: iwrcgop028.fzk.de:1094//.
>>050503 14:08:04 001 Xrd: Create Access to server granted.
>>050503 14:08:04 001 Xrd: Create Opening the remote file /tmp/testfile.dat
>>050503 14:08:04 001 Xrd: Create File opened succesfully.
>>050503 14:08:04 001 Xrd: main root://iwrcgop028.fzk.de//tmp/testfile.dat 
>>--> /dev/null
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>050503 14:08:04 27096 Xrd: LogConnection Processing unsolicited response
>>050503 14:08:04 27096 Xrd: ConnectionMgr Processing unsolicited response
>>.... (repeated in total 41984 times for my 1GB test file)
>>050503 14:08:32 27096 Xrd: LogConnection Processing unsolicited response
>>Caching info: MissRate=0.611176 MissCount=2625 ReadsCounter=4295
>>Caching info: BytesUsefulness=0.198375 BytesSubmitted=3280128680 
>>BytesHit=650623344
>>
>>If I apply my InfiniBand patch, it looks quite similar. Please let me know if 
>>this helps. 
>>
>>Thank's,
>>Ulrich
>>
>>Am Dienstag 03 Mai 2005 01:34 nachmittags/abends schrieb Fabrizio Furano:
>>
>>>Hi,
>>>
>>> maybe you don't miss anything. I suspect that you found a way (Infiniband)
>>>to greatly confuse the trivial async read ahead algorithm I coded for the
>>>first version of the async read ahead. I may be wrong, of course.
>>>In any case xrdcp does not need read ahead at all so it's better if I make
>>>it an option, as it's needed in other cases also. Async read ahead could be
>>>a help if you have an application which processes the data, otherwise it's
>>>useless.
>>>
>>> If you set the debug level to a higher value (-DI DebugLevel 1), 1 should
>>>be sufficient, xrdcp will print you the cache statistics, so we can learn
>>>something to tune this strange async thing if that is the source of the
>>>overhead. Would you do this on your setup please?
>>>
>>>Fabrizio
>>>
>>>On Tuesday 03 May 2005 12:00 pm, Ulrich Schwickerath wrote:
>>>
>>>>Hi,
>>>>
>>>>I made a quick first test running the new version on an GB Ethernet link.
>>>>I just copy a 1GByte file from my server to local /dev/null. While with
>>>>20050413-0433 I got
>>>>
>>>>$ time  bin/arch/xrdcp   root://iwrcgtest.fzk.de//tmp/testfile.dat
>>>>/dev/null
>>>>
>>>>real    0m10.909s
>>>>user    0m1.150s
>>>>sys     0m0.720s
>>>>
>>>>with the new version I get:
>>>>
>>>>[schwicke@iwrcgop027:/home/schwicke/Progamming/xrootd]$ time
>>>>bin/arch/xrdcp root://iwrcgtest.fzk.de//tmp/testfile.dat /dev/null
>>>>[xrootd] Total 1024.00 MB       |====================| 100.00 % [36.6
>>>>Mb/s]
>>>>
>>>>real    0m29.377s
>>>>user    0m1.670s
>>>>sys     0m1.190s
>>>>
>>>>Going to quiet mode does not help (my first thought since I work
>>>>remotely): $ time  bin/arch/xrdcp -s
>>>>root://iwrcgtest.fzk.de//tmp/testfile.dat /dev/null
>>>>
>>>>real    0m28.147s
>>>>user    0m1.150s
>>>>sys     0m0.380s
>>>>
>>>>The test is done on Sun V20z dual Opterons, both for server and client,
>>>>using the onboard GE link.
>>>>
>>>>Did I miss something ?
>>>>
>>>>Thank's,
>>>>Ulrich
>>>>
>>>>On Monday 02 May 2005 17:04, Peter Elmer wrote:
>>>>
>>>>>  Hi All,
>>>>>
>>>>>  There is now a new development version of xrootd (20050502-0000).
>>>>>This version contains a lot of new code, so it is meant for testing
>>>>>rather than production use. For production use, please try version
>>>>>20050328-0656 instead.
>>>>>
>>>>>  The changes include:
>>>>>
>>>>>   o compilation fixes for gcc4
>>>>>   o updates to XrdClient for async read-ahead
>>>>>   o updates to xrdcp from Andreas Peters
>>>>>   o Many updates to scripts in XrdMon package
>>>>>   o Code cleanup fixes (from Gregory Sharp)
>>>>>   o Several fixes for minor bugs, etc.
>>>>>
>>>>>  We should start testing this (including compilation on the full set
>>>>>of ROOT platforms) as I'd like to try to turn out a new production
>>>>>release in the next week or two.
>>>>>
>>>>>  For the full set of changes and links to rpms/tarballs to download
>>>>>see the the xrootd web page and/or version history:
>>>>>
>>>>>   http://xrootd.slac.stanford.edu
>>>>>   http://xrootd.slac.stanford.edu/xrootd.History
>>>>>
>>>>>Let us know if there are problems.
>>>>>
>>>>>                                 thanks,
>>>>>                                   Pete
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>-- Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22)
>>>>>767-4644 Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23,
>>>>>Switzerland
>>>>>-----------------------------------------------------------------------
>>>>>--
>>
>>-- 
>>__________________________________________
>>Dr. Ulrich Schwickerath
>>Forschungszentrum Karlsruhe
>>GRID-Computing and e-Science
>>Institut for Scientific Computing (IWR)
>>P.O. Box 36 40
>>76021 Karlsruhe, Germany
>>
>>Tel: +49(7247)82-8607
>>Fax: +49(7247)82-4972 
>>
>>e-mail: [log in to unmask]
>>PGP DH/DSS Key: ID 0xCEB9826F
>>Fingerprint: 5537 8473 CD26 507E 8EE2  BAAF 98E2 FD16 CEB9 826F
>>__________________________________________
> 
> 
> 
> 
> -------------------------------------------------------------------------
> Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22) 767-4644
> Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
> -------------------------------------------------------------------------


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