Grid node high disk latency on c:\users\GridNodeUser\AppData

I run disk node under a windows user (GridNodeUser) and I notice it has high response times (164ms) on my C-Drive (SSD) for e.g.
C:\Users\GridNodeUser\AppData\Local and ...\Local\Temp and also ...\Local\NCrunch\hashcache
And one process causing this is "nCrunch.BuildHost46.x86.exe".

I have my ncrunch grid node workspace/snapshots on my E-drive (2xSSD raid-0).

Wouldn't it be good to define a "temporary" location for NCrunch as well (or whatever is causing above disk access to my C-Drive)?
(i.e. I would want above high latency times to go to a RAMDisk if possible)

Thanks.

Are you certain that this is being caused by nCrunch.BuildHost? I would expect that only the engine process should be interacting with the hash cache.

The hash cache does, unfortunately, need to be stored somewhere persistently. This cache is used to allow the node to quickly identify matching snapshots for connecting clients, and it does contain relevant data that can be quite expensive to reconstruct.

Do you have any information about whether the interactions with the hash cache are read or write? Also, which files under Local\Temp are being used? If this is being done by the buildhost, it may well be MSBuild tasks doing this.

I have not seen this issue after I reported it so I will get back to you with further details if I stumble upon it again.