Hi Igor,
it's almost the same. I'm considering startup + connection. I'm using
Ignite 2.4. The node excel is only client, and I have only a server node
on an other machine in my organization, and I cannot see particular
activity of cpu or network.
Thanks,
F.D.
On Tue, May 22, 2018 at 11:00 AM Igor Sapego <isap...@apache.org> wrote:
> Hi,
>
> Try using "TcpDiscoveryStaticIpFinder" instead of
> "TcpDiscoveryMulticastIpFinder".
>
> Does it take 1 min for connection only or for start up + connection?
>
> Best Regards,
> Igor
>
> On Tue, May 22, 2018 at 11:45 AM, F. D. <free.devel...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm trying to use Ignite to develop an internal system of data
>> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
>> the C# binding.
>>
>> When try to connect it consumes a lot of time (~1 min.), this is my
>> simple app.config:
>>
>>
>>
>>
>> > type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core"/>
>>
>>
>>
>>
>>
>>
>>http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
>> localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
>> gridName="IMIStreamer">
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>10.200.20.90:47500..47509
>>
>>
>>
>>
>>
>>
>> > sku=".NETFramework,Version=v4.5.2"/>
>>
>>
>>
>>
>> Is it possibile to reduce this time of connection?
>> I've tried to use the thin client, but in this client there's no
>> continuous query (and need it, because I want to be reactive when a cache
>> change).
>>
>> Thanks in advance for your help,
>>F.D.
>>
>>
>