Dual JVM - Revision history

JaroslavTulach at 08:20, 22 April 2026

2026-04-22T08:20:38Z

←Older revision		Revision as of 08:20, 22 April 2026
Line 2:		Line 2:


-		+	=== [[Apache]] Arrow ===

	The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.		The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.

JaroslavTulach at 08:20, 22 April 2026

2026-04-22T08:20:15Z

←Older revision		Revision as of 08:20, 22 April 2026
Line 6:		Line 6:
	The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.		The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.

-	Pros: similar system was an enterprise only feature called GraalVM Isolates	+	* Pros: similar system was an enterprise only feature called GraalVM Isolates
-	Cons: the Isolates are being open sourced and further work may be needed to align with them	+	* Cons: the Isolates are being open sourced and further work may be needed to align with them

JaroslavTulach: /* Dual JVM Mode */

2026-04-22T06:43:07Z

Dual JVM Mode

←Older revision		Revision as of 06:43, 22 April 2026
Line 1:		Line 1:
-	~~==== Dual~~ JVM ~~Mode ====~~	+	A heroic effort was needed to marry the fast start of the [[Enso]] engine (to be attributed to AOT compilation) with the need to dynamically load JVM classes. The effort is being called a ''"dual JVM"'' (see [https://docs.google.com/presentation/d/1f0ygesiiUbMe3rEXVonDPzLI0TyKIWkMeLyhh4okkKE slides]) because there are two [[Java]] virtual machines running in the single [[Enso]] process communicating effectively with each other.
		+
		+

-	A heroic effort was needed to marry the fast start of the [[Enso]] engine (to be attributed to AOT compilation) with the need to dynamically load JVM classes. The effort is being called a [https://docs.google.com/presentation/d/1f0ygesiiUbMe3rEXVonDPzLI0TyKIWkMeLyhh4okkKE dual JVM] because there are two Java virtual machines running in the single Enso process communicating effectively with each other.

	The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.		The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.

JaroslavTulach: New page: ==== Dual JVM Mode ==== A heroic effort was needed to marry the fast start of the Enso engine (to be attributed to AOT compilation) with the need to dynamically load JVM classes. The ...

2026-04-22T06:41:33Z

New page: ==== Dual JVM Mode ==== A heroic effort was needed to marry the fast start of the Enso engine (to be attributed to AOT compilation) with the need to dynamically load JVM classes. The ...

New page

==== Dual JVM Mode ====

A heroic effort was needed to marry the fast start of the [[Enso]] engine (to be attributed to AOT compilation) with the need to dynamically load JVM classes. The effort is being called a [https://docs.google.com/presentation/d/1f0ygesiiUbMe3rEXVonDPzLI0TyKIWkMeLyhh4okkKE dual JVM] because there are two Java virtual machines running in the single Enso process communicating effectively with each other.

The essential use-case was driven by the need to exchange columnar data between those two JVMs. We decided to support zero copy exchange of data (mostly) in the Apache Arrow format between those two JVMs. Performance seems to be sufficiently good and the format allows us to integrate with other Arrow-ready systems like Pandas when the time comes.

Pros: similar system was an enterprise only feature called GraalVM Isolates
Cons: the Isolates are being open sourced and further work may be needed to align with them