Performance and Runtime
| ←Older revision | Revision as of 08:46, 30 April 2026 | ||
| Line 2: | Line 2: | ||
| - | == | + | == The Year of Dual JVM! == |
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
* Towards '''Dual JVM'''! | * Towards '''Dual JVM'''! | ||
** [https://github.com/enso-org/enso/issues/13172 Dual NI + JVM Mode for Loading Libraries] | ** [https://github.com/enso-org/enso/issues/13172 Dual NI + JVM Mode for Loading Libraries] | ||
| Line 18: | Line 11: | ||
** [https://github.com/enso-org/enso/pull/14099 Fibonacci benchmark comparing hosted and dual JVM modes] | ** [https://github.com/enso-org/enso/pull/14099 Fibonacci benchmark comparing hosted and dual JVM modes] | ||
** [https://github.com/enso-org/enso/pull/14232 Support for dynamic loading of native JVMs] | ** [https://github.com/enso-org/enso/pull/14232 Support for dynamic loading of native JVMs] | ||
| + | ** [https://github.com/enso-org/enso/pull/14309 Arrow like storage over ByteBuffer to allow dual JVM buffer exchange] | ||
| + | |||
| + | == Other Performance and Runtime Improvements == | ||
| + | |||
| + | * Optimizing Enso distribution by not [https://github.com/enso-org/enso/issues/11483 Wasting 100MB by Standard.Image] | ||
| + | * Rely more on ''Y.js'': [https://github.com/enso-org/enso/issues/11477 execute Y.js and Insight together] & co. | ||
| + | ** [https://github.com/enso-org/enso/pull/13178 Launching ydoc-server together with language-server] | ||
| + | ** [https://github.com/enso-org/enso/pull/13206 Channel connecting two JVM instances] | ||
| + | * Usual speed ups like | ||
| + | ** [https://github.com/enso-org/enso/issues/11846 Benchmark ... and speed it up] | ||
| + | ** [https://github.com/enso-org/enso/pull/12720 60% speed up....] | ||
* Tighten up execution semantics with [https://github.com/enso-org/enso/pull/12655 ... when interrupting Enso execution] | * Tighten up execution semantics with [https://github.com/enso-org/enso/pull/12655 ... when interrupting Enso execution] | ||