On 1/22/2013 3:34 PM, Nick wrote:
> We've run into an issue with the TSVNCache process when icon overlays are enabled for network drives. Basically what we're seeing is, for no known reason at all, TSVNCache goes out to the attached network drives and starts caching everything it can find - on one system, this resulted in ~11GB of data read from our server by the process in around an hour. As soon as we disabled the option for icon overlays on network drives, the behavior went away. Also, during this time, there were no Explorer windows open on the client - everything was closed down. Does this sound like normal/expected behavior?
>
> For the second part of the question, perhaps this is an Enhancement Request, is there a way that the network portion of the icon overlays could be more finely tuned? For example, you can add exclusions, but what about having some sort of manual caching trigger (and disabling the automatic caching for the network side) or specifying *exactly* which network folders you want the icon overlays to be present on, rather than assuming they should be present on all attached network drives? We have shared network locations where multiple users store working copies of SVN repos, but each user doesn't need to see overlays for all of the other users on those network drives - only their own. Under the current config, they'd have to go exclude everything except their own. Any chance that could be tweaked?
>
> ------------------------------------------------------
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3045346
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
>
While I have nothing to offer in the way of a technical (never mind
"official") explanation, I'm relatively certain that this issue has been
bandied-about dozens of times on this list in the last year alone.
While I do not speak for them, I am skeptical that the developers will
have any interest in modifying the overlay caching implementation such
that network drives are excluded by default. For everybody who feels the
same way you do there will be somebody else who has a melt-down because
network drive caching is "broken" out-of-the-box.
With respect to the second issue, you could always modify the filesystem
permissions such that each user does not have access to the other users'
working copies. While that's not to say that this method is preferable,
it's a short-term solution, provided that the users do not, in fact,
have a need to access each others' working copies.
Best regards,
-Ben
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3045353
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-22 21:57:59 CET