Skip to content

feat: performance improvements inspired by SAQ#29

Draft
oliverlambson wants to merge 1 commit intomainfrom
feat/locking-improvements
Draft

feat: performance improvements inspired by SAQ#29
oliverlambson wants to merge 1 commit intomainfrom
feat/locking-improvements

Conversation

@oliverlambson
Copy link
Contributor

@oliverlambson oliverlambson commented Jun 21, 2025

TODO:

  • handle db migrations
  • review

@oliverlambson oliverlambson force-pushed the feat/locking-improvements branch 3 times, most recently from b0079f5 to 1a23f41 Compare June 21, 2025 22:47
@oliverlambson oliverlambson force-pushed the feat/locking-improvements branch from 1a23f41 to 0cdd947 Compare June 21, 2025 22:58
@hmax
Copy link

hmax commented Aug 8, 2025

Hey, are there any plans/rough timeline for this one? I am in need of some of the features that you implement in this PR and have actually implemented something similar in my fork (but would definitely prefer an upstream version).

Maybe there's something I could help with to make it move forward?

@oliverlambson
Copy link
Contributor Author

Hey, are there any plans/rough timeline for this one? I am in need of some of the features that you implement in this PR and have actually implemented something similar in my fork (but would definitely prefer an upstream version).

Maybe there's something I could help with to make it move forward?

We're actually using a different worker/messaging system now internally, so maintaining this library is lower priority at the moment.

This PR is in a half-done state and I hadn't finished thinking through the implications of the changes. If you'd like finish it (or open a similar new one), I would be happy to review it and merge if all looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants