crdt-benchmarks VS automerge

Compare crdt-benchmarks vs automerge and see what are their differences.

automerge

A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically. (by automerge)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
crdt-benchmarks automerge
8 45
399 3,081
- 5.5%
0.0 9.1
2 months ago 13 days ago
JavaScript JavaScript
GNU General Public License v3.0 or later MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

crdt-benchmarks

Posts with mentions or reviews of crdt-benchmarks. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-22.
  • JSON-joy CRDT benchmarks, 100x speed improvement over state-of-the-art
    4 projects | news.ycombinator.com | 22 May 2023
    Author of Yjs here. I'm all for faster data structures. But only benchmarking one dimension looks quite fishy to me. A CRDT needs to be adequate at multiple dimensions. At least you should describe the tradeoffs in your article.

    The time to insert characters is the least interesting property of a CRDT. It doesn't matter to the user whether a character is inserted within .1ms or .000000001ms. No human can type that fast.

    It would be much more interesting to benchmark the time it takes to load a document containing X operations. Yjs & Yrs are pretty performant and conservative on memory here because they don't have to build an index (it's a tradeoff that we took consciously).

    When benchmarking it is important to measure the right things and interpret the results somehow so that you can give recommendations when to use your algorithm / implementation. Some things can't be fast/low enough (e.g. time to load a document, time to apply updates, memory consumption, ..) other things only need to be adequate (e.g. time to insert a character into a document).

    Unfortunately, a lot of academic papers set a bad trend of only measuring one dimension. Yeah, it's really easy to succeed in one dimension (e.g. memory or insertion-time) and it is very nice click-bait. But that doesn't make your CRDT a viable option in practice.

    I maintain a set of benchmarks that tests multiple dimensions [1]. I'd love to receive a PR from you.

    [1]: https://github.com/dmonad/crdt-benchmarks

  • CRDT-richtext: Rust implementation of Peritext and Fugue
    17 projects | news.ycombinator.com | 18 May 2023
    Diamond types author here! Congratulations on getting your crdt working! It’s lovely to see a new generation of CRDTs which have decent performance.

    And nice stuff implementing peritext! I’d love to do the same in diamond types at some point. You beat me to it!

    Im building a little repository of real world collaborative editing traces to use when benchmarking, comparing and optimising text based CRDTs[1]. The automerge-perf editing trace isn’t enough on its own. And we’re increasingly converging on a format for multi user concurrent editing traces too[2]. It’d be great to add some rich text editing traces in the mix if you’re interested in recording something, so we can also compare how peritext performs in different systems.

    Anyway, welcome to the community! Love to have more implementations around!

    https://github.com/josephg/crdt-benchmarks

    https://github.com/dmonad/crdt-benchmarks/issues/20

  • Cloudant/IBM back off from FoundationDB based CouchDB rewrite
    3 projects | news.ycombinator.com | 12 Mar 2022
    So yes, a particularly large document is not the norm but it can happen.

    JavaScript CRDTs can be quite performant, see the Yjs benchmarks: https://github.com/dmonad/crdt-benchmarks

  • Automerge: A JSON-like data structure (a CRDT) that can be modified concurrently
    12 projects | news.ycombinator.com | 20 Feb 2022
  • Automerge: a new foundation for collaboration software [video]
    13 projects | news.ycombinator.com | 10 Dec 2021
  • Show HN: SyncedStore CRDT – build multiplayer collaborative apps for React / Vue
    11 projects | news.ycombinator.com | 8 Dec 2021
  • 5000x Faster CRDTs: An Adventure in Optimization
    8 projects | news.ycombinator.com | 31 Jul 2021

automerge

Posts with mentions or reviews of automerge. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-10.

What are some alternatives?

When comparing crdt-benchmarks and automerge you can also consider the following projects:

diamond-types - The world's fastest CRDT. WIP.

yjs - Shared data types for building collaborative software

electric - Local-first sync layer for web and mobile apps. Build reactive, realtime, local-first apps directly on Postgres.

y-websocket - Websocket Connector for Yjs

teletype-crdt - String-wise sequence CRDT powering peer-to-peer collaborative editing in Teletype for Atom.

FluidFramework - Library for building distributed, real-time collaborative web applications

y-crdt - Rust port of Yjs

slate-yjs - Yjs binding for Slate

automerge-rs - Rust implementation of automerge [Moved to: https://github.com/automerge/automerge]

SyncedStore - SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.