10000 Investigate IPC for collaboration server · Issue #9280 · outline/outline · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Investigate IPC for collaboration server #9280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
tommoor opened this issue May 22, 2025 — with Slack · 2 comments
Open

Investigate IPC for collaboration server #9280

tommoor opened this issue May 22, 2025 — with Slack · 2 comments
Labels
A1 Priority customer issues collaborative editing Issues that are stepping stone work towards collab editing performance

Comments

@tommoor Slack
Copy link
Member
tommoor commented May 22, 2025

Enable usage of all threads with IPC
@linear Linear
Copy link
linear bot commented May 22, 2025

OLN-1119 Investigate IPC for collaboration server

@tommoor tommoor added performance collaborative editing Issues that are stepping stone work towards collab editing A1 Priority customer issues labels May 23, 2025
@tommoor
Copy link
Member Author
tommoor commented May 23, 2025 •
edited
Loading

Initial investigations are not too promising, in order to shard documents between processes / threads we'd need to either:

  • Remove throng and completely manage the process forking and message passing in userland
  • Keep throng/cluster and allow round robin connections but pass messages between all processes via the master process
  • Ke 600C ep throng/cluster and allow round robin connections but pass messages between all processes via Redis/Nats

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A1 Priority customer issues collaborative editing Issues that are stepping stone work towards collab editing performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tommoor
0