coracle/flotilla
1
6
Fork 23
Code Issues 42 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Improve performance #182

New Issue
Closed
opened 2026-04-09 20:08:47 +00:00 by hodlbod · 4 comments
hodlbod commented 2026-04-09 20:08:47 +00:00
Owner
Copy Link
Copy Source

Run some profiling and figure out quick wins for improving performance. This might include:

  • Putting less stuff in storage
  • Putting less stuff in the repository (see welshman/app/index for the current logic)
  • Doing less/more debouncing

The main bottleneck seems to be GC pressure, which means memory is the problem, not computation. This might come from using too many timers, or from storing too many events in memory. One strategy I have in mind is to set up a separate repository per space so we don't have to constantly reconcile tracker and repository when deriving events for a particular url.

Solutions should not compromise simplicity and maintainability. It would be easy to make a mess fixing this, but long term I want to swap out the underlying libraries which should solve this at a more fundamental level. This issue may have multiple assignees and multiple PRs with different solutions.

Run some profiling and figure out quick wins for improving performance. This might include: - Putting less stuff in storage - Putting less stuff in the repository (see welshman/app/index for the current logic) - Doing less/more debouncing The main bottleneck seems to be GC pressure, which means memory is the problem, not computation. This might come from using too many timers, or from storing too many events in memory. One strategy I have in mind is to set up a separate repository per space so we don't have to constantly reconcile tracker and repository when deriving events for a particular url. Solutions should not compromise simplicity and maintainability. It would be easy to make a mess fixing this, but long term I want to swap out the underlying libraries which should solve this at a more fundamental level. This issue may have multiple assignees and multiple PRs with different solutions.
hodlbod added this to the Current milestone 2026-04-09 20:08:47 +00:00
hodlbod added the dev label 2026-04-09 20:08:47 +00:00
priyanshu_bharti commented 2026-04-09 20:15:39 +00:00
Contributor
Copy Link
Copy Source

hii @hodlbod can I work on this issue

hii @hodlbod can I work on this issue
hodlbod commented 2026-04-09 20:17:48 +00:00
Author
Owner
Copy Link
Copy Source

Please do

Please do
priyanshu_bharti was assigned by hodlbod 2026-04-09 20:17:58 +00:00
userAdityaa commented 2026-04-09 20:52:09 +00:00
Collaborator
Copy Link
Copy Source

Hey @priyanshu_bharti, if you face any issues (or) just need any help, I would be happy to take this on.

Hey @priyanshu_bharti, if you face any issues (or) just need any help, I would be happy to take this on.
theAnuragMishra commented 2026-04-09 21:04:49 +00:00
Contributor
Copy Link
Copy Source

Let's treat this as a tracking issue for sub-issues working towards optimizations in different parts?

Let's treat this as a tracking issue for sub-issues working towards optimizations in different parts?
👍 1
priyanshu_bharti was unassigned by hodlbod 2026-04-09 21:40:09 +00:00
hodlbod referenced this issue from a commit 2026-04-10 17:40:22 +00:00
Improve performance #182:
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label dev
Milestone
No items
No Milestone Current
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#182
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?