I've tried reproduce the behaviour on my side (used your code snippet above) but without success. Could you profile your application by fly recorder? You can use the following settings https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-flightrecorder-settings .
On Fri, Mar 31, 2017 at 4:21 PM, Nikolai Tikhonov <[email protected]> wrote: > Let's try to increase the following parameter TcpCommunicationSpi# > setUnacknowledgedMessagesBufferSize to 1_000_000. > > On Fri, Mar 31, 2017 at 2:03 PM, yishchuk <[email protected]> wrote: > >> I've enabled GC logging as you suggested, and attached the results. >> >> gc-L01.log >> <http://apache-ignite-users.70518.x6.nabble.com/file/n11606/gc-L01.log> >> gc-L02.log >> <http://apache-ignite-users.70518.x6.nabble.com/file/n11606/gc-L02.log> >> gc-L03.log >> <http://apache-ignite-users.70518.x6.nabble.com/file/n11606/gc-L03.log> >> gc-L05.log >> <http://apache-ignite-users.70518.x6.nabble.com/file/n11606/gc-L05.log> >> gc-L06.log >> <http://apache-ignite-users.70518.x6.nabble.com/file/n11606/gc-L06.log> >> >> gc-CLIENT.log >> <http://apache-ignite-users.70518.x6.nabble.com/file/n11606/ >> gc-CLIENT.log> >> >> last call took on server L06 3.21271845s, and on the client - >> 30.815496906s >> >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Huge-delays-while-returning-data-back- >> from-remote-callable-s-tp11561p11606.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
