RE: Performance degradation in embed mode

Hello! It’s incredible! Thank you for help! Dmitriy From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com] Sent: Tuesday, August 14, 2018 6:02 PM To: user@ignite.apache.org Subject: Re: Performance degradation in embed mode Hello! It looks like you have debug enabled when running inside

Re: Performance degradation in embed mode

Hello! It looks like you have debug enabled when running inside Apache Tomcat. Turning DEBUG on will make Ignite spend a lot of time and RAM building debug messages. Please make sure to turn DEBUG off, at least for org.apache.ignite packages. Regards, -- Ilya Kasnacheev 2018-08-14 11:45

Re: Performance degradation in embed mode

Hello Ilya, Thank you for the replay. So, I did ran the test after context initialization, but the problem is persists. dump during test execution dump after running the test

Re: Performance degradation in embed mode

Hello! In your thread dump I observe that context creation is still underway (org.apache.catalina.mbeans.MBeanFactory.createStandardContext) No load is passed to Apache Ignite yet. Regards, -- Ilya Kasnacheev 2018-08-11 12:09 GMT+03:00 Dmitriy : > Hello Igniters, > > I'm using an spring web

Performance degradation in embed mode

Hello Igniters, I'm using an spring web application with the embed Ignite cache. When we run in unit-tests, the insertion time into the cache is about 10 000 values/seconds. But when the application is running on the Apache Tomcat server, the insert is very slow (about 5 minutes). The