atlas-debug unusable slow performance

[Dirk Brutscher]

When developing an addon I currently encounter the problem, that running atlas-debug to start a local Confluence 6.10.0 is unuable slow. Loading a page sometime takes more than 30s. How can I debug this performance problem? And how can I give more memory resources to the atlas-debug instance (I think the 1GB may one of the problems).

[AnnWorley · Accepted solution]

Hi Dirk,

From this article it looks like you can pass the min and max memory parameters to your instance with the --jvmargs flag: atlas-debug.

For example, the following would set it to 4GB: 

-Xms4096m -Xmx4096m

 Since you are developing an add-on I wanted to share this link, too: Helpful resources for developers building Atlassian apps

Thanks,

Ann

[Dirk Brutscher]

Ok, thanks, seems to work. No performance beast but must better than before :-)

[Ture Hoefner]

The syntax for the command with flags was painful enough for me to figure out that I thought I'd post it here so folks can copy/paste:

atlas-debug --maven-plugin-version 8.2.0 --jvmargs "-Xms4096m -Xmx4096m"

[Robert Varga]

This question was already answered but I want to share what helped in my case. I reduced number of active breakpoints (IntelliJ IDEA) and it made a huge difference.