Speaking of #ActivityPub things, I realized that one of my previous design decisions for the custom storage functionality of #GoActivityPub: to include both OAuth2 and ActivityPub API interfaces is now biting me in the butt when I'm trying to increase parallelism on the sqlite storage implementation.
Currently there's a single sqlite db for the whole instance - so write locking happens a lot.
1/2
I want to improve things by having every actor on the instance owning their own db, so locks happen only if somehow there are multiple activities happening concurrently for that same actor - which is less likely.
However the OAuth2 access API have all functionality compatible with a per actor logic.
Add comment