[ https://issues.apache.org/jira/browse/IGNITE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-3568: ----------------------------------- Summary: .NET: Start JVM externally (was: .NET: Start JVM externally.) > .NET: Start JVM externally > -------------------------- > > Key: IGNITE-3568 > URL: https://issues.apache.org/jira/browse/IGNITE-3568 > Project: Ignite > Issue Type: Task > Components: platforms > Affects Versions: 1.6 > Reporter: Vladimir Ozerov > Priority: Critical > Labels: .net > > Currently we start JVM inside .NET process. This is not good for several > reasons: > 1) Broken isolation - only one JVM can exist per process. This way it is > impossible to start two Ignite instances with different JVM options. > 2) JVM startup is expensive, cluster connection is expensive, and process > must host both Java and .NET heaps. Should we have external JVM to connect > to, we would allow for truly thin clients, when dozens thin processes will be > able to work with the same client. We already see growing demand for this > feature, -- This message was sent by Atlassian JIRA (v6.3.4#6332)