f limit in the server
to avoid this situation.
El mar, 30 nov 2021 a las 15:12, Eduard Llull Pou (<
eduard.ll...@bluekiri.com>) escribió:
> Hi Stephen,
>
> I have not gathered the logs produced around the time I generated the
> memory dump. I will dump the memory again when we r
gt; of memory errors happening around the time of other problems? Are you
> seeing network issues? Do you see “long JVM pauses” in the logs?
>
> On 30 Nov 2021, at 12:28, Eduard Llull Pou
> wrote:
>
> Hi Ibrahim,
>
> We'll test it but even if your suggested parameters
following line executed on Ignite server node?
> _ignite.GetOrCreateNearCache
>
> On Wed, Feb 5, 2020 at 11:44 AM Eduard Llull wrote:
>
>> Hi everyone,
>>
>> We have been using Ignite and Ignite.NET in the recent months in a
>> project. We currently have six Igni
Hi everyone,
We have been using Ignite and Ignite.NET in the recent months in a project.
We currently have six Ignite servers (started with ignite.sh) and a bunch
of thick clients split in two .NET Core application deployed in 30 servers.
We store de-normalized data in the Ignite data grid: one o
se with .NET Core 3.0, we plan to
> make the next Ignite release fully compatible with it.
>
> Thanks,
> Pavel
>
>
>
> On Wed, Sep 18, 2019 at 1:48 PM Eduard Llull wrote:
>
>> Hi everyone,
>>
>> Almost a month ago I claimed that one of our application
Hi everyone,
Almost a month ago I claimed that one of our application that use the
Ignite.NET thick client we were getting SIGSEGVs and SIGABRT, and changing
to the thin client it fixed that problem but the performance was severally
impacted [
http://apache-ignite-users.70518.x6.nabble.com/NET-thi
> one of the server nodes it's connected to. While the thick client always
> goes to a node that keeps a key. The proxy is a bottleneck and that's why
> you see such a performance drop.
>
> -
> Denis
>
>
> On Thu, Aug 22, 2019 at 11:49 PM Eduard Llull wrote:
Hello everyone,
We have just developed a gRPC service in .NET core that performs a bunch of
cache gets for every RPC. We've been using the Apache.NET nuGet starting
the Ignite node in client mode (thick client) but we just changed it to use
the thin client and we see much much worse response times
