Print

---

Hi, Does anyone know why xrootd 3rd party copy HTTPS implementation uses 65536 for ofs_read, but if I read it to local dir - it uses 1048576? Can it be configurable per site (or made to be configurable) - or are there any implementation constraints?
Thanks!

a) gfal-copy https://<endpoint>/filename <localfilename> on xrootd logs I see:230126 15:09:13 024 jbalcas.8:31@login-1 ofs_read: 1048576@0 fn=/store/user/jbalcas/testSourceFile0230126 15:09:13 024 jbalcas.8:31@login-1 ofs_read: 1048576@1048576 fn=/store/user/jbalcas/testSourceFile0
b) gfal-copy (third party copy) https://<endpoint>/filename https://<endpoint1>/filename:230126 15:19:44 024 jbalcas ofs_read: 65536@0 fn=/store/user/jbalcas/testSourceFile0230126 15:19:44 024 jbalcas ofs_read: 65536@65536 fn=/store/user/jbalcas/testSourceFile0230126 15:19:44 024 jbalcas ofs_read: 65536@131072 fn=/store/user/jbalcas/testSourceFile0230126 15:19:44 024 jbalcas ofs_read: 65536@196608 fn=/store/user/jbalcas/testSourceFile0
--