Hmm, I wasn&#39;t anticipating that my comment would produce such a reaction. <br>
Xcache has nothing to do with high performance disk or whatver. The simple <br>
fact that Xcache is multithreaded and optmized for data files puts it <br>
ahead of squid for data applications, especially when resources may be<br>
potentially scarce. It&#39;s generally a 1-for-1 replacement. I don&#39;t see any <br>
issue in suggesting that from a resource optimization perspective that <br>
Xcache would be a better choice.<br>
<br>
Andy<br>
<br>
On Wed, 23 Oct 2019, DrDaveD wrote:<br>
<br>
&gt; In what way?  Are you suggesting that we put an xcache server at every site like we do squids?  Assuming they&#39;re all configured with high performing and relatively large disk caches, that&#39;s not something we can expect small sites to do.  Squids could be configured with high disk performance too, but that&#39;s more expensive and it wasn&#39;t needed for their current applications which have a very high hit rate and small working set, so that&#39;s why they have slow and small disks.  Edgar&#39;s use case is also high hit rate and small working set, so it fits naturally into the ordinary cvmfs existing infrastructure.  @bbockelm&#39;s design for the cvmfs integration with xcache was intended for partially shared &amp; larger files, not for the completely shared smaller files of Edgar&#39;s use case.<br>
&gt;<br>
&gt; -- <br>
&gt; You are receiving this because you were mentioned.<br>
&gt; Reply to this email directly or view it on GitHub:<br>
&gt; https://github.com/xrootd/xrootd/issues/1073#issuecomment-545618099<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/xrootd/xrootd/issues/1073?email_source=notifications&amp;email_token=AA7NRDVD6J6A7YUASVLT4RLQQC2WJA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECC23JI#issuecomment-545631653">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AA7NRDSL57V6LEUH7FEQXILQQC2WJANCNFSM4JDSBUTA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AA7NRDQBWB42EDIJ3LH4IS3QQC2WJA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECC23JI.gif" height="1" width="1" alt="" /></p>
<!cript type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1073?email_source=notifications\u0026email_token=AA7NRDVD6J6A7YUASVLT4RLQQC2WJA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECC23JI#issuecomment-545631653",
"url": "https://github.com/xrootd/xrootd/issues/1073?email_source=notifications\u0026email_token=AA7NRDVD6J6A7YUASVLT4RLQQC2WJA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECC23JI#issuecomment-545631653",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
<br>
<hr>
<p align="left">
Use REPLY-ALL to reply to list</p>
<p align="center">To unsubscribe from the XROOTD-DEV list, click the following link:<br>
<a href="https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1" target="_blank">https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1</a>
</p>