dd3c6d1303
After some discussion with PVH I realise that the repo structure in the last reorg was very rust-centric. In an attempt to put each language on a level footing move the rust code and project files into ./rust |
||
|---|---|---|
| .. | ||
| benches | ||
| src | ||
| .gitignore | ||
| automerge-1.0.js | ||
| automerge-js.js | ||
| automerge-rs.js | ||
| automerge-wasm.js | ||
| baseline.js | ||
| Cargo.toml | ||
| editing-trace.js | ||
| edits.json | ||
| Makefile | ||
| package.json | ||
| README.md | ||
Edit trace benchmarks
Try the different editing traces on different automerge implementations
Automerge Experiement - pure rust
make rust
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
make wasm
Automerge Experiment - JS wrapper
make js
Automerge 1.0 pure javascript - new fast backend
This assumes automerge has been checked out in a directory along side this repo
node automerge-1.0.js
Automerge 1.0 with rust backend
This assumes automerge has been checked out in a directory along side this repo
node automerge-rs.js
Baseline Test. Javascript Array with no CRDT info
make baseline