Print

Print


Hi Andy,
sorry I am a bit confused here.

One year go (19/11/2021) Elvin Sindrilaru from CERN, who was helping us with debugging precisely this issue, wrote us:

"After having a chat with Michal and Andy Hanushevsky (xrootd server side developer), we realized there is one easy configuration change that you could do to avoid having too many small read requests done against the back-end. Therefore, could you please set the following in your configuration and restart the daemon:

xrootd.async nofs"

At that time, we add

xrootd.async off

Following that suggestion, we changed xrootd.async off to xrootd.async nosf, and saw great improvements.
Now, are you saying we should set it back to
xrootd.async off
?

Thanks,
lucia


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <xrootd/xrootd/issues/1799/1311743620@github.com>

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