https://answers.axonivy.com/questions/4379/engine-performance-profiling<p>Dear Ivy Team</p> <p>My test setup is as follows : 4 CPU (i7, 3GHz), Xms128m, Xmx2048m</p> <p>2 Browsers, every 3 seconds a click on the UI during 60 seconds</p> <p>1 With visualvm it shows that Ivy spent approx 16s with reading, the issue is I can not quantify how much data it is (since your performance / rest client logging is not working). But my guess is, it can only be a few hundred KB in total.</p> <p>=&gt; 16s seem to me a lot, can you confirm my results ?</p> <p><img alt="alt text" src="https://answers.axonivy.com/upfiles/Unbenannt.PNG"></p> <p>2 Rest Client - java &gt; Ivy.rest() : is Ivy.rest() client pooled ? (since the Rest Clients are pretty heavy weight they should be pooled otherwise memory consumption skyrockets and also performance will degrade if they are used like in a micro services architecture)</p> <p>=&gt; Ivy.rest() did you do any performance analysis ? Is this the "required" way of using Rest Client in Ivy ?</p>enWed, 04 Mar 2020 10:28:41 -0500https://answers.axonivy.com/questions/4379/engine-performance-profiling/4443<p>joined analysis of the issues initiated. public discussion of this specific issues which only arise with an unsupport rest clients scenario are of no value for a broader audience - so we freeze the thread for now.</p>SupportIvyTeamWed, 04 Mar 2020 10:28:41 -0500https://answers.axonivy.com/questions/4379/engine-performance-profiling/4443https://answers.axonivy.com/questions/4379/engine-performance-profiling#4383<p>Just had another look on client connection pooling in our rest stack. It's true that Jersey (our used JAX-RS impl) supports connection pooling when using Apache Http Client as connection provider. Apache is our default provider. But we do not explicitly define a HttpClientconnectionPool as shown here: <a href="https://github.com/jersey/jersey/commit/80c8c7013c52ddf9012932676d1048c79133d0f2#diff-2d8626e00eee8ac6a1e5aaa6ab815086R165">https://github.com/jersey/jersey/commit/80c8c7013c52ddf9012932676d1048c79133d0f2#diff-2d8626e00eee8ac6a1e5aaa6ab815086R165</a></p> <p>So no, we do not have this kind of pooling. If this is a real world issue, when using ivy api, and you need more flexibility to enable a pooling. Let us know.</p>Reguel WermelingerMon, 10 Feb 2020 02:58:36 -0500https://answers.axonivy.com/questions/4379/engine-performance-profiling#4383https://answers.axonivy.com/questions/4379/engine-performance-profiling#4382<p>Well it is around since quite a while: the first public release was here <a href="https://developer.axonivy.com/releases/ivy/6.2.0/documents/doc/newAndNoteworthy/NewAndNoteworthyDesigner.html">https://developer.axonivy.com/releases/ivy/6.2.0/documents/doc/newAndNoteworthy/NewAndNoteworthyDesigner.html</a> ... so around 3 years + ... therefore it is included in all supported platform versions today</p>Reguel WermelingerFri, 07 Feb 2020 09:32:43 -0500https://answers.axonivy.com/questions/4379/engine-performance-profiling#4382https://answers.axonivy.com/questions/4379/engine-performance-profiling#4381<blockquote> <blockquote> <p>something homebrew</p> </blockquote> </blockquote> <p>When has Ivy.rest() been introduced to the public ?</p>John MoserFri, 07 Feb 2020 08:59:50 -0500https://answers.axonivy.com/questions/4379/engine-performance-profiling#4381https://answers.axonivy.com/questions/4379/engine-performance-profiling#4380<ol> <li>what is in ch.xperline.luz.components.RestClient ? Is it relying upon platform APi or something homebrew? If it's not platform code, we can not support it.</li> <li>We are not aware of any performance/memory issues with the way we create Restclient instances. There are several caching mechanisms in charge though. If there are performance issues anyway (caused by the way we manage rest clients) we'd gladly improve it.</li> </ol>Reguel WermelingerFri, 07 Feb 2020 05:13:44 -0500https://answers.axonivy.com/questions/4379/engine-performance-profiling#4380