Hi Raja,
I think the fist and most important aspect here is to understand the
locality aspects of the vector reads. One way is to turn on monitoring a
for a bit and gather statistics on these reads. This will more
clearly define the solution parameters going forward.
Andy
On Tue, 11 Aug 2020, Raja Nandakumar wrote:
> Many tanks for the comments. From a non-expert point of view (not having understood everything, though I am trying), I have a couple of questions
>
> 1. Where do we go from here / what next to try?
> 2. I note that we have so far been using disk proxy in our tests. Using a memory proxy also showed a similar issue. But is it worth re-considering using memory proxies, assuming that the design is very different from disk proxy and likely has different configuration options?
>
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1259#issuecomment-671821130
—
You are receiving this because you were mentioned.
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/1259#issuecomment-672095000",
"url": "https://github.com/xrootd/xrootd/issues/1259#issuecomment-672095000",
"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
