Print

Print

In what way? Are you suggesting that we put an xcache server at every site like we do squids? Assuming they're all configured with high performing and relatively large disk caches, that's not something we can expect small sites to do. Squids could be configured with high disk performance too, but that's more expensive and it wasn't needed for their current applications which have a very high hit rate and small working set, so that's why they have slow and small disks. Edgar's use case is also high hit rate and small working set, so it fits naturally into the ordinary cvmfs existing infrastructure. @bbockelm's design for the cvmfs integration with xcache was intended for partially shared & larger files, not for the completely shared smaller files of Edgar's use case.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1073?email_source=notifications\u0026email_token=AA7NRDRLF2ADI77JF2QYDGDQQCWRRA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCXRMY#issuecomment-545618099", "url": "https://github.com/xrootd/xrootd/issues/1073?email_source=notifications\u0026email_token=AA7NRDRLF2ADI77JF2QYDGDQQCWRRA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCXRMY#issuecomment-545618099", "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