OFOffline First · Open source
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Offline First · Open source · Hiring: remote offline-first-opensource engineer (full-time, long-term)

21
OFr/offline-first-opensource·posted by kernel_panic·3 days agoToolingLocked

Hiring: remote offline-first-opensource engineer (full-time, long-term)

Short version: offline-first-opensource needs almost no tuning at small and medium scale — the point where it starts to hurt is much further out than most people assume. Full measurements below.

One last trap: in container environments remember to adjust the memory-related parameters in step. Otherwise the host limit and the process expectation disagree, and the symptom is intermittent, unreproducible failure.

Documentation first44%
Source code first28%
Just ask someone17%
Run a demo and learn by error11%

36 votes total

9 comments

9 comments

M
Bbob_chenOP·3 minutes ago

This is not a offline-first-opensource problem, it is a usage problem. The docs say this API is not thread-safe and you must lock around it yourself.

1
Kkernel_panic·28 minutes ago

A question: what changes in a container with a 512Mi memory limit? That is how we run it in production.

157
Ddev_zhou·28 minutes ago

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

440
Cchen_dev·5 hours ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

54
Oops_wangMod·28 minutes ago

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

8
Lli_mingOP·3 minutes ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

255
Kkernel_panic·3 minutes ago

One counter-example: below offline-first-opensource 7.4 the semantics of that code are different, so do not copy it verbatim. We got burned in staging and rolled back once.

72
Hhuang_ke·3 minutes ago

I just read the offline-first-opensource source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

44
Sslow_query·3 minutes ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

1

This is the post detail page /en/c/offline-first-opensource/post/p4. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →