Wow, that is great. Thanks! With regard to experienced slowdown, of the management console I assume, does that get better if you apply name-based filtering to the views?
Thanks John [rg] <https://www.redpointglobal.com/> John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761<tel:+1%207209385761> | john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com> From: Roskvist Anton <anton.roskv...@volvo.com> Sent: Thursday, November 10, 2022 12:32 PM To: users@activemq.apache.org Subject: RE: Practical limit on #queues in Artemis *** [Caution] This email is from an external source. Please use caution responding, opening attachments or clicking embedded links. *** Hello John, For reference, one of the environments I’m maintaining currently uses around 3.5k active destinations. The broker cluster is running on relatively modest servers without any issues. I will say though that at this point there has been some noticeable slowdowns in precisely the areas that Justin mentioned… that being said the clients (running on separate servers) report an average publish latency of ~0.8ms on the actual queues. That’s quite impressive I think. Br, Anton From: John Lilley <john.lil...@redpointglobal.com.INVALID<mailto:john.lil...@redpointglobal.com.INVALID>> Sent: den 9 november 2022 15:56 To: users@activemq.apache.org<mailto:users@activemq.apache.org> Subject: RE: Practical limit on #queues in Artemis CAUTION: This email originated from outside of the organization. If suspicious, please report it. Thanks Justin! I’ll run some tests and just see what happens. John [rg]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redpointglobal.com%2F&data=05%7C01%7Canton.roskvist%40volvo.com%7Ca30d60c4defd4257fa7708dac262a8ec%7Cf25493ae1c9841d78a330be75f5fe603%7C0%7C0%7C638036026240483171%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RyuoSBmj%2FvQSF0NPHcV2Tb8qKqf04Y%2Bpr44iSA8aTVs%3D&reserved=0> John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761<tel:+1%207209385761> | john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com> From: Justin Bertram <jbert...@apache.org<mailto:jbert...@apache.org>> Sent: Tuesday, November 8, 2022 10:04 PM To: users@activemq.apache.org<mailto:users@activemq.apache.org> Subject: Re: Practical limit on #queues in Artemis *** [Caution] This email is from an external source. Please use caution responding, opening attachments or clicking embedded links. *** There is certainly a practical limit, but I doubt anybody has a clear view of what it is. I think you're more likely to hit pain points with management (e.g. the web console) before the queues themselves cause problems. Justin On Fri, Nov 4, 2022 at 2:16 PM John Lilley <john.lil...@redpointglobal.com.invalid<mailto:john.lil...@redpointglobal.com.invalid>> wrote: Greetings, We create a queue per “job” and there can be a lot of jobs. We tend to keep them around for a while (like an hour) to service job status after the job is complete, but this can result in a lot of mostly-idle queues. Is there a practical limit at which Artemis becomes unhappy (low memory, sluggish performance)? I’m sure it depends on VM sizing, but let’s just say that we have Artemis running in a K8S pod with 4GB memory available and 4vcpus. I’m only looking for an order-of-magnitude ballpark. Something like “no more than N per GB memory” would be great. Thanks John [rg]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fwww.redpointglobal.com%252f%26c%3DE%2C1%2Ca8aL6_GO7_wvHtc4lTsWrsJVcK2R3i5wfLc7ihagaX-6tQm79faPPdZ48z0APtj7ZSpJvkDiSterVPAT44gVh4dMlx31S0lajTRltfql%26typo%3D1&data=05%7C01%7Canton.roskvist%40volvo.com%7Ca30d60c4defd4257fa7708dac262a8ec%7Cf25493ae1c9841d78a330be75f5fe603%7C0%7C0%7C638036026240483171%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4wyMy4eNE3hI2zABvg1oHV7MXxwkzkfgo9nyfNAbj4I%3D&reserved=0> John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761<tel:+1%207209385761> | john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com> PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint. PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint. This email message (including its attachments) is confidential and may contain privileged information and is intended solely for the use of the individual and/or entity to whom it is addressed. If you are not the intended recipient of this e-mail you may not disseminate, distribute or copy this e-mail (including its attachments), or any part thereof. If this e-mail is received in error, please notify the sender immediately by return e-mail and make sure that this e-mail (including its attachments), and all copies thereof, are immediately deleted from your system. Please further note that when you communicate with us via email or visit our website we process your personal data. See our privacy policy for more information about how we process it: https://www.volvogroup.com/en-en/privacy.html<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.volvogroup.com%2fen-en%2fprivacy.html&c=E,1,1l_pi5EBgs-jikH5_gANZQ-bFwp2PBOJDaN57Z7QEA8Gbt6Rq_xt2w-bFGe3Gc6vNy593p_ghkaNRtE5j1OiuUoFb4oSn1dj-2RyFDmkhrYzGHHN0Yj0&typo=1&ancr_add=1> PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint.
