Print

Print

I certainly can close this out but I really want to point out this is not a "connection" limit here. It's really what I would call a job limit. Each copy is a job and it uses resources across many domains (i.e. disk, network, memory, etc). So, what we are limiting is the number of these can run at the same time which is quite reasonable and is quite similar to what batch systems do. If we were just talking about one resource utilization then I would agree with you. But this is not the case here and trying to come up with a limit across all of these domains is not really practical. That's why a copy limit winds up being a reasonable solution.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1601#issuecomment-1265618015", "url": "https://github.com/xrootd/xrootd/issues/1601#issuecomment-1265618015", "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