2 Aug
2019
2 Aug
'19
11:19 a.m.
Thanks, Fred!
In my opinion this comes down to the DB queries. None of them should be taking an
unreasonable amount of time (so much time that a normal-ish amount of workers will
suffice), and there should not be too many of them.
—
Sent from mobile, with due apologies for brevity and errors.
On Aug 1, 2019, at 9:07 PM, Fred Posner
<fred(a)palner.com> wrote:
On 8/1/19 7:52 PM, jay binks wrote:
--snip--
I have removed pike, and replicated without pike loaded.
Just for clarity sake, adding more workers 100% fixed the issue.
What im really seeking is a way to monitor for this scenario so I can graph it and not
get caught out by surprise.
In the last day or 2, ive found that some of the DB Queries in my kam config were taking
longer than they should ( for a few reasons ), so this will be a largly contributing
factor, however ... it still comes back to, how do I monitor for packets being dropped
because there was no worker.
Thanks all
Jay
...
Alex Balashov wrote a fantastic article on this:
http://www.evaristesys.com/blog/tuning-kamailio-for-high-throughput-and-per…
Lots of good tips and explanations in there... with a tl/dr; being there's no
straight forward answer to reaping maximum benefit.
For example, you're using DB... which many of us do. Are you using HTABLE to cache
information that can be cached? Perhaps instead of running a query on every hit, you can
run it every 5 min... or cache the password and save some lookups on authentication, etc.
Anyway, lots of ways of approaching this and the article above is a great place to
start.
Fred Posner
fred(a)qxork.com
https://qxork.com
Direct/SMS: +1 (224) 334-3733
Direct/SMS: +1 (336) 439-3733
Need Fred? Call Fred. 336-HEY-FRED
Matrix: @fred:matrix.lod.com
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users