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

Limit in memory messages #183

New Issue
Closed
opened 2026-04-09 21:15:10 +00:00 by theAnuragMishra · 2 comments
theAnuragMishra commented 2026-04-09 21:15:10 +00:00
Contributor
Copy Link
Copy Source

Currently we do not have any limits to how many messages live in memory. This means the memory usage could in theory grow indefinitely.
Would it be okay to keep only n most recent messages in memory and pop off the least recent one whenever a new one arrives?
Part of #182

Currently we do not have any limits to how many messages live in memory. This means the memory usage could in theory grow indefinitely. Would it be okay to keep only `n` most recent messages in memory and pop off the least recent one whenever a new one arrives? Part of #182
hodlbod commented 2026-04-09 21:25:27 +00:00
Owner
Copy Link
Copy Source

All events are in memory anyway (hopefully shared references, although I don't know how to validate that). A virtual scroll component might be helpful for reducing how many messages are in the dom at a time, although it may be a pretty difficult thing to get right (we do lots of scroll management and sometimes navigate to a particular point in time within a room). But feel free to explore and see what might work.

All events are in memory anyway (hopefully shared references, although I don't know how to validate that). A virtual scroll component might be helpful for reducing how many messages are in the dom at a time, although it may be a pretty difficult thing to get right (we do lots of scroll management and sometimes navigate to a particular point in time within a room). But feel free to explore and see what might work.
theAnuragMishra commented 2026-04-10 21:43:27 +00:00
Author
Contributor
Copy Link
Copy Source

Understandable yeah. JS defaults to references for objects so basically shared TrustedEvents.

Understandable yeah. JS defaults to references for objects so basically shared TrustedEvents.
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
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#183
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?