automerge/edit-trace
2022-04-07 12:22:28 +01:00
..
benches Make edit-trace vals be a string and use splice_text 2022-04-07 12:22:28 +01:00
src Make edit-trace vals be a string and use splice_text 2022-04-07 12:22:28 +01:00
.gitignore splice 2021-11-30 11:29:51 -08:00
automerge-1.0.js cleaned up edit trace, added docs 2021-12-13 09:20:49 -05:00
automerge-js.js Add makefile to run edit-traces 2022-04-01 13:56:15 +01:00
automerge-rs.js Add makefile to run edit-traces 2022-04-01 13:56:15 +01:00
automerge-wasm.js Add makefile to run edit-traces 2022-04-01 13:56:15 +01:00
baseline.js Add makefile to run edit-traces 2022-04-01 13:56:15 +01:00
Cargo.toml bump edition from 2018 to 2021 2022-02-03 14:38:21 -05:00
editing-trace.js profiling and seq_tree 2021-11-29 17:27:47 -07:00
edits.json profiling and seq_tree 2021-11-29 17:27:47 -07:00
Makefile Add makefile to run edit-traces 2022-04-01 13:56:15 +01:00
package.json profiling and seq_tree 2021-11-29 17:27:47 -07:00
README.md Add criterion benchmarks for Rust (#248) 2021-12-19 14:59:40 +00:00

Try the different editing traces on different automerge implementations

Automerge Experiement - pure rust

  # cargo --release run

Benchmarks

There are some criterion benchmarks in the benches folder which can be run with cargo bench or cargo criterion. For flamegraphing, cargo flamegraph --bench main -- --bench "save" # or "load" or "replay" or nothing can be useful.

Automerge Experiement - wasm api

  # node automerge-wasm.js

Automerge Experiment - JS wrapper

  # node automerge-js.js

Automerge 1.0 pure javascript - new fast backend

This assume automerge has been checked out in a directory along side this repo

  # node automerge-1.0.js

Automerge 1.0 with rust backend

This assume automerge has been checked out in a directory along side this repo

  # node automerge-rs.js

Automerge Experiment - JS wrapper

  # node automerge-js.js

Baseline Test. Javascript Array with no CRDT info

  # node baseline.js