What is it synchronizing with? Bear in mind you can’t mix Kamailio versions
when doing DMQ
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
On Fri, 9 Feb 2024 at 17:17, Ben Kaufman via sr-users <
sr-users(a)lists.kamailio.org> wrote:
Just checking to see if anyone had any ideas about
tuning on this feature.
*From:* Ben Kaufman via sr-users <sr-users(a)lists.kamailio.org>
*Sent:* Thursday, February 1, 2024 8:38 AM
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
*Cc:* Ben Kaufman <bkaufman(a)bcmone.com>
*Subject:* [SR-Users] High CPU with DMQ on ARM64 (graviton) - Tuning
values for DMQ worker_usleep
*CAUTION:* This email originated from outside the organization. *Do not
click links or open attachments* unless you recognize the sender and know
the content is safe.
I encountered a behavior with DMQ using excessive CPU when running
kamailio 5.8 on AWS Graviton processors (running in Docker on Amazon Linux
2023), even on an otherwise idle system. Finding the issue below pointed
me towards using polling. I set the value for worker_usleep to 1000 as a
test, and that seems to have resolved the CPU issue, but I have no idea of
what a “good” value is for this setting, and 1000 was simply the example
present in the documentation. My specific use case for DMQ is
synchronizing USRLOC data for ~7,500 users, registering with expiration
times of 60 – 300 seconds with 7 – 9 nodes on the DMQ bus. Any general
recommendations on tuning values for this setting?
https://github.com/kamailio/kamailio/issues/822
Regards,
Kaufman
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe: