Print

Print

I tried client/server combinations from 5.5.3 and our build of the master branch from last week. The results are the same.
I tried with defaults, xrootd.async off, xrootd.async off nosf ... results are almost always the same. There must be some bottlenecks server side with multiplexed/parallel connections, because with individual connections it is so much faster ... ok, when my target can write 'only' 1 GB/s I actually don't see a difference between the three ways to copy, but with NVMes as target it makes already a difference.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <xrootd/xrootd/issues/1938/1451546918@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1938#issuecomment-1451546918", "url": "https://github.com/xrootd/xrootd/issues/1938#issuecomment-1451546918", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

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