mirror of
https://github.com/enso-org/enso.git
synced 2024-11-23 16:18:23 +03:00
8e49255d92
# Important Notes
#### The Plot
- there used to be two kinds of benchmarks: in Java and in Enso
- those in Java got quite a good treatment
- there even are results updated daily: https://enso-org.github.io/engine-benchmark-results/
- the benchmarks written in Enso used to be 2nd class citizen
#### The Revelation
This PR has the potential to fix it all!
- It designs new [Bench API](88fd6fb988) ready for non-batch execution
- It allows for _single benchmark in a dedicated JVM_ execution
- It provides a simple way to wrap such an Enso benchmark as a Java benchmark
- thus the results of Enso and Java benchmarks are [now unified](https://github.com/enso-org/enso/pull/7101#discussion_r1257504440)
Long live _single benchmarking infrastructure for Java and Enso_!
720 B
720 B
| layout | title | category | tags | order | |||
|---|---|---|---|---|---|---|---|
| section-summary | Debugger | debugger |
|
0 |
Enso Debugger
This folder contains all documentation pertaining to the debugging facilities used by Enso, broken up as follows:
- The Enso Debugger Protocol: The protocol for the REPL Debugger.
- Chrome devtools debugger: A guide how to debug Enso code using Chrome devtools.
- Debugging Enso and Java code at once: A step-by-step guide how to debug both Enso and Java code in a single debugger.
- Debugging Engine (Runtime) only Java code: A guide how to debug the internal Engine Java code.