I have reproduced this issue in a fresh Artemis installation. First I created a local Artemis instance on my laptop, created 3000 queues, and it performed perfectly without any issues. Then I created a virtual server in a Proxmox VE (it runs on a desktop-grade hardware). The virtual machine was configured with 1 CPU and 4 Gb RAM, OS is Debian 12. Java heap settings are default (Xms512m, Xmx2G). The symptoms were similar to those I have in the work environment, except the CPU was not loaded at 100% all the time (only for 2-3 seconds). Loading of the console first page took about 140 seconds.
I have captured some thread dumps: one before logon, several dumps during loading the first page, and one after the page was loaded. If attachments are not allowed here, I can upload to some file sharing service. пн, 7 апр. 2025 г. в 21:34, Justin Bertram <jbert...@apache.org>: > I tried to reproduce this using a fresh instance of 2.40.0 with 2,500 > queues defined in broker.xml (thanks to a bash script), but the console > loaded in just a few seconds. > > I then created a fresh instance of 2.39.0 with 2,500 queues defined in > broker.xml. Then I ran "artemis data exp" to export the data and then > created a fresh instance of 2.40.0 and ran "artemis data imp" to import > those queues. After that I opened the console and it loaded in a few > seconds. > > Could you perhaps grab a few thread dumps from the broker when you see it > running at 99% and share links to them? > > Also, are there further details you can share about your use-case? You must > be doing something different in your environment to get that result than > what I'm doing. > > > Justin > > > > On Mon, Apr 7, 2025 at 10:24 AM Alexander Milovidov <milovid...@gmail.com> > wrote: > > > Hi All, > > > > Has anyone installed ActiveMQ Artemis 2.40.0 in an environment with a > > significant number of addresses and queues? > > I have several problems with performance of the new Artemis console and > > message broker. I have installed Artemis 2.40.0 and imported data from a > > file which was exported from the test environment with approx. 2500 > queues. > > > > 1. When opening the Artemis console for the first time, it takes about > > 200-250 seconds to load. > > 2. When the console is loading, the server's processor is loaded at 99%. > > After it loads, the CPU load is decreased to 3-5%. > > > > This virtual machine has 1 processor, 4 Gb of memory, 2 Gb java heap, and > > there were no problems running Artemis 2.39.0 with the same > configuration. > > After increasing to 4 CPU, 8 Gb, the console is still loading 150 > seconds, > > and 4 CPUs are loaded to 25%. Increasing the heap to 4 Gb did not change > > anything. > > > > Is there any way to increase the performance of the new console? > > > > Another problem is that the bugfix ARTEMIS-5248 caused audit logs to grow > > significantly. We are using the LDAPLogin module with Active Directory > > authentication and authorization based on membership of the user. Each > user > > in our company's active directory domain can be a member of 100-400 > domain > > groups, and each group is a role. The list of roles is logged in each > audit > > log message, and the size of each message can be significantly large (up > to > > 10 Kb). Unfortunately, disabling audit logging does not affect the > overall > > performance of the web console. > > > > I will later try to reproduce this issue in a fresh installation by > > creating 2500 empty queues. > > > > -- > > Regards, > > Alexander > > >
<<attachment: artemis_thread_dumps.zip>>
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
