Conversation

We’re sharing some stuff that might be interesting, on how we’re improving our architecture to make sure Linear stays fast even for larger organisations. notion.so/linearapp/Impr TLDR performance is hard and we still have some work to do!

Quote Tweet

Linear

@linear

· May 20, 2021

Changelog: Over the last two weeks we have been heads down improving performance for certain larger Linear workspaces which have experienced slowness. While your workspace might not be affected, the improvements should make Linear faster for everyone linear.app/changelog/2021

Show this thread

Also, cc

you talked about offline first apps a while back – maybe you’ll find our writeup of interest.

Andy Matuschak

@andy_matuschak

May 21, 2021

Thanks, this makes a lot of sense, and it's helpful to see the details. I'd be curious to learn more about your approach to syncing!

Andreas Eldh

@eldh

May 21, 2021

Maybe deserves a blog post of its own but it’s just a big ass table with all diffs, and we stream those to clients as they connect. Previously we had a limit on how many messages you could receive before doing a full bootstrap but now we just send all diffs.

Andy Matuschak

@andy_matuschak

Replying to

@eldh

How do you handle reconciliation with your diff table? i.e. multiple clients making changes while offline, then coming back online

6:35 PM · May 21, 2021TweetDeck

Replying to

Last one wins. We’re going to add CRDT:s pretty soon for things like issue descriptions but haven’t really had the need to do anything more advanced for most of our data yet.

Andy Matuschak

@andy_matuschak

May 21, 2021

Got it. And you determine the set ofdiffs which need to be uploaded/downloaded using a client-specific sequence number? Or are yet-to-be-persisted local diffs sequestered in some separate store?

Show replies