mirror of https://github.com/enso-org/enso.git synced 2025-01-02 12:30:20 +03:00

History

Jaroslav Tulach f53696eda4 sbt runEngineDistribution ...args... to build and execute the engine (#5609 ) Automating the assembly of the engine and its execution into a single task. If you are modifying standard libraries, engine sources or Enso tests, you can launch `sbt` and then just: ``` sbt:enso> runEngineDistribution --run test/Tests/src/Data/Maybe_Spec.enso [info] Engine package created at built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev [info] Executing built-distribution/enso-engine-...-dev/bin/enso --run test/Tests/src/Data/Maybe_Spec.enso Maybe: [5/5, 30ms] - should have a None variant [14ms] - should have a Some variant [5ms] - should provide the `maybe` function [4ms] - should provide `is_some` [2ms] - should provide `is_none` [3ms] 5 tests succeeded. 0 tests failed.unEngineDistribution 4s 0 tests skipped. ``` the [runEngineDistribution](`3a581f29ee/docs/CONTRIBUTING.md (running-enso)`) `sbt` input task makes sure all your sources are properly compiled and only then executes your enso source. Everything ready at a single press of Enter. # Important Notes To debug in chrome dev tools, just add `--inspect`: ``` sbt:enso> runEngineDistribution --inspect --run test/Tests/src/Data/Maybe_Spec.enso E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/7JsgjXlntK8 ``` everything gets build and one can just attach the Enso debugger.		2023-02-16 21:37:12 +00:00
..
Unnamed	Add Language Server benchmarking tool (#3578 )	2022-07-22 14:12:52 +00:00
ignore_responses.txt	Update apply-edit benchmark to use lazy visualization (#3642 )	2022-08-15 07:11:51 +00:00
init.bin	Add Language Server benchmarking tool (#3578 )	2022-07-22 14:12:52 +00:00
init.txt	Update apply-edit benchmark to use lazy visualization (#3642 )	2022-08-15 07:11:51 +00:00
input.txt	Add Language Server benchmarking tool (#3578 )	2022-07-22 14:12:52 +00:00
README.md	sbt runEngineDistribution ...args... to build and execute the engine (#5609 )	2023-02-16 21:37:12 +00:00

README.md

apply-edit

Benchmark for command that applies text edit. It sends the text/applyEdit message and waits for the visualization message on binary WebSocket.

Run

Build Enso distribution. Start the Language Server and redirect ouput to language-server.log

sbt runEngineDistribution \
  --log-level trace \
  --server \
  --root-id 6f7d58dd-8ee8-44cf-9ab7-9f0454033641 \
  --path $(pwd)/tools/language-server/wstest/benchmarks/apply-edit/Unnamed/ \
  --rpc-port 30616 \
  --data-port 30717 \
  2>&1| tee language-server.log

Run the test and redirect output to wstest.log

cargo run -p wstest -- \
  --binary-socket ws://127.0.0.1:30717 \
  --init-binary-socket tools/language-server/wstest/benchmarks/apply-edit/init.bin \
  --init-text-socket tools/language-server/wstest/benchmarks/apply-edit/init.txt \
  --wait-after-init 10000 \
  --ignore-text-socket-responses tools/language-server/wstest/benchmarks/apply-edit/ignore_responses.txt \
  --input tools/language-server/wstest/benchmarks/apply-edit/input.txt \
  --input-expects-binary-responses \
  --warmup-iterations 100 \
  --wait-after-warmup 3000 \
  --benchmark-iterations 100 \
  ws://127.0.0.1:30616 \
  2>&1| tee wstest.log

Analyze logs

cargo run -p logstat -- \
  --median \
  --spec tools/language-server/logstat/apply-edit-spec.txt \
  --wstest-log wstest.log \
  language-server.log

Example output

avg [min..max] (of 100 records)
0ms [0..0] [main] wstest sent bench request [{ "jsonrpc": "2.0", "method": "text/applyEdit"
0ms [0..3] [org.enso.jsonrpc.JsonRpcServer] Received text message: { "jsonrpc": "2.0", "met
0ms [0..1] [org.enso.languageserver.protocol.json.JsonConnectionController] received handle
1ms [0..2] [org.enso.languageserver.runtime.RuntimeConnector] received handled Request(None
0ms [0..1] [enso] Executing command: EditFileCmd...
14ms [11..24] [enso] Job EnsureCompiledJob finished in 23 ms.
1ms [1..9] [enso] Visualisation computed 524dd815-b652-4bbe-b9f2-26b35d17993a.
0ms [0..1] [org.enso.languageserver.runtime.ContextRegistry] received handled Visualisation
0ms [0..1] [main] wstest handled response [<binary>]
17ms [15..33] Total