Print

Print

AFAIR the max vector chunk sizes come from the xrootd protocol, and the HTTP code tries to fit the more liberal HTTP specs into that, limiting the overhead. I am puzzled by the idea to work around the vector size limitations imposed (and well documented) by the xrootd protocol

Which client is generating these requests? I don't think that a vector read makes too much sense for large chunks

That's correct, that's why I'm asking what is wrong with the algorithm : its behavior, or its shape? Thanks for your comment @ffurano !

—
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/1976/1577064611@github.com>

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