No, that is not the solution and that value should not change. It is set to that value for a very critical reason and changing it would cause a number of really more serious issues. The 2MB default is calculated to be the best value for most cases. The correct solution is to fix this on he http side. This is an HTTP side problem not a server side problem. In fact a read element can be 2MB-now but the http side insists on 128KB which is here the problem comes from. Also, mind you the value for xrd.buffers you saw is specific to EOS the common use case is much smaller and changing it has very serious side-effects outside of EOS. Why don't we discuss this when I am at CERN next week.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

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