Multiplayer Latency Optimization Task
Budget: $15 – $25 USD
Here’s the room I’m working with (live demo):
https://multiplayer.templates.tldraw.dev/test-room-Yz6HBSaZAr6NaTKe6N6JE?d=v0.0.393.500.VxUvEXm6dnKy6gEUq-n80
The template itself is solid, but the moment several people jump in, every stroke, drag, or shape movement starts to feel sticky. My priority is improving server performance, with latency reduction as the single most important metric. I’m not looking to add new mechanics or touch the UI right now—just want the current experience to feel instantly responsive.
The stack is TypeScript, tldraw, CRDT-style sync over WebSockets, running on a plain Node back-end. I need someone who can profile the current round-trip, spot the bottlenecks (serialization, message size, N → N fan-out, socket handling, or even hosting location), and then ship code that brings interaction latency to a level where two users on opposite US coasts barely notice the delay.
Deliverables
• Short benchmarking script or dashboard showing baseline latency with 10, 50, and 100 concurrent users
• Optimized server code (or config) pushed to the repo, clearly commented
• Post-change benchmark proving a measurable improvement (aiming for <50 ms median round-trip in the same test)
• One-page write-up explaining what was changed and why, so future contributors can maintain the gains
If you’ve tuned real-time apps before—WebSockets, WebRTC, Redis pub/sub, edge runtimes, or similar—you’ll feel right at home here. Let’s make this canvas feel truly real-time.
https://multiplayer.templates.tldraw.dev/test-room-Yz6HBSaZAr6NaTKe6N6JE?d=v0.0.393.500.VxUvEXm6dnKy6gEUq-n80
The template itself is solid, but the moment several people jump in, every stroke, drag, or shape movement starts to feel sticky. My priority is improving server performance, with latency reduction as the single most important metric. I’m not looking to add new mechanics or touch the UI right now—just want the current experience to feel instantly responsive.
The stack is TypeScript, tldraw, CRDT-style sync over WebSockets, running on a plain Node back-end. I need someone who can profile the current round-trip, spot the bottlenecks (serialization, message size, N → N fan-out, socket handling, or even hosting location), and then ship code that brings interaction latency to a level where two users on opposite US coasts barely notice the delay.
Deliverables
• Short benchmarking script or dashboard showing baseline latency with 10, 50, and 100 concurrent users
• Optimized server code (or config) pushed to the repo, clearly commented
• Post-change benchmark proving a measurable improvement (aiming for <50 ms median round-trip in the same test)
• One-page write-up explaining what was changed and why, so future contributors can maintain the gains
If you’ve tuned real-time apps before—WebSockets, WebRTC, Redis pub/sub, edge runtimes, or similar—you’ll feel right at home here. Let’s make this canvas feel truly real-time.