 |
 |
@bbockelm Interesting links! The documentation of xrootd made me think this option would be sufficiently safe and favourable. Also, I was more thinking about "the other end", e.g. FTS streaming data to hundreds of sites in parallel with a many-Gbps link. On our end, we actually have 6 dataservers with 16 real cores, so we won't be saturated. The peak CPU load I saw from an xrootd with 1 GBit/s connectivity was about 35-40% (on a single core), of which most was probably not SSL. So I agree, it might not be needed (at least not at an almost receive-only end), but the documentation talks rather optimistic about this flag (too ptimistic maybe?), and the missing auth by role is still a bug. But we'll likely stay with https now anyways unless somebody starts to complain about high load ;-). -- 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/745#issuecomment-398090053 ######################################################################## 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