For direct transfers, xrdcp seems to use a fixed 8 MiB block size when requesting data over the network. We've seen a problem in which a remote server misbehaves if the requested data is 4 MiB, but seems to work fine if the block size is 8 MiB (see #1454). I think it would be helpful if `xrdcp` supported some mechanism that allowed a user to specify the size of read blocks. This might be to optimise network transfers, but also easy reproduction of problems such as in #1454. It would also allow a site to validate their endpoint works correctly at different requested block sizes. I note that there is an environment variable `XRD_XCPBLOCKSIZE`; however, it wasn't clear to me (from the man page) whether this has the desired effect. Its description refers to an "extreme copy transfer": a term that is not defined in the man page. (I don't consider this urgent. I'm creating the issue just so it doesn't get lost.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1491 ######################################################################## 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