[GH-ISSUE #3] Locking improvement #2

New issue

Closed

opened 2026-05-23 08:25:01 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-23 08:25:01 -06:00

Owner

Originally created by @appy-one on GitHub (Jan 28, 2021).
Original GitHub issue: https://github.com/appy-one/acebase/issues/3

Originally assigned to: @appy-one on GitHub.

Locking is now implemented by only allowing 1 write at the same time, while also denying read requests during writes. Back in the old days, locking was path based: if 2 paths did not cross they were allowed to proceed in parallel. This was disabled later on because it resulted in deadlocks in particular cases. While only allowing 1 write lock at a time is ok, many read requests should be allowed to proceed during writes. Even better if deadlocks could be prevented; multiple simultaneous writes would become possible again. This has to be investigated.

Originally created by @appy-one on GitHub (Jan 28, 2021). Original GitHub issue: https://github.com/appy-one/acebase/issues/3 Originally assigned to: @appy-one on GitHub. Locking is now implemented by only allowing 1 write at the same time, while also denying read requests during writes. Back in the old days, locking was path based: if 2 paths did not cross they were allowed to proceed in parallel. This was disabled later on because it resulted in deadlocks in particular cases. While only allowing 1 write lock at a time is ok, many read requests should be allowed to proceed during writes. Even better if deadlocks could be prevented; multiple simultaneous writes would become possible again. This has to be investigated.