[jira] [Commented] (IGNITE-3568) .NET: Start JVM externally

["Denis Magda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716688#comment-15716688 ] 

Denis Magda commented on IGNITE-3568:
-------------------------------------

[~vozerov],

Sharing a JVM process for a number of .NET nodes might be a bottleneck depending on the workload. This needs to be considered. Have you done any investigation around this?

Next, do we need to make a new inter-process communication protocol as a part of this activity?

> .NET: Start JVM externally
> --------------------------
>
>                 Key: IGNITE-3568
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3568
>             Project: Ignite
>          Issue Type: New Feature
>          Components: platforms
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Priority: Minor
>              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)