mirror of
https://github.com/enso-org/enso.git
synced 2024-12-25 05:21:53 +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_!
1.1 KiB
1.1 KiB
| layout | title | category | tags | order | ||
|---|---|---|---|---|---|---|
| section-summary | Infrastructure | infrastructure |
|
0 |
Infrastructure
The Enso runtime runs on the GraalVM which is a version of the JVM. This folder contains all documentation pertaining to Enso's infrastructure, which is broken up as follows:
- sbt: The build tools that are used for building the project.
- Java 11: Description of changes related to the Java 11 migration.
- Native Image: Description of the Native Image build used for building the launcher native binary.
- Rust: Description of integration of the Scala project with the Rust components.
- Upgrading GraalVM: Description of steps that have to be performed by each developer when the project is upgraded to a new version of GraalVM.
- Benchmarks: Description of the benchmarking infrastructure used for measuring performance of the runtime.
- Logging: Description of an unified and centralized logging infrastructure that should be used by all components.