mirror of
https://github.com/enso-org/enso.git
synced 2024-11-22 22:10:15 +03:00
701bba6504
The ultimate goal is to reduce the method calls necessary for `Vector.map`. # Important Notes - I managed to reduce the number of Java stack frames needed for each `Vector.map` call from **150** to **22** (See https://github.com/enso-org/enso/pull/11363#issuecomment-2432996902) - Introduced `Stack_Size_Spec` regression test that will ensure that Java stack frames needed for `Vector.map` method call does not exceed **40**. |
||
|---|---|---|
| .. | ||
| benchmarks.md | ||
| logging.md | ||
| native-image.md | ||
| README.md | ||
| rust.md | ||
| sbt.md | ||
| upgrading-graalvm.md | ||
| 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.
- Native Image: Description of the Native Image build
used for building the
ensoupnative 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.