lock contention caused by sharing prerequisites
Status: Beta
Brought to you by:
worden
Menu
▾
▴
#215 lock contention caused by sharing prerequisites
When lots of projects connect to a popular "service" project (we have an example called Autodhs), each of them needs to lock that project in order to do its work. They don't need the service project very often, and when they do, the work done there is typically very quick. But they may be doing substantial work in their own directories, and the service project will be locked for all that time. This means that all those different downstream projects, essentially unrelated, have to take turns doing their work. Not so good.
Related
Discussion
Anonymous
#72 PE should do read locking whenever possible seems relevant. But how to make it work?!
I mean: it's clear enough how to use it for read-only operations. But that doesn't help for write operations in the downstream directory.
I wonder if it would be possible to make
make-in-other-projectdo locking??? If so, we could skip locking the upstream projects on the way in and let those calls do it only when needed.