The OP didn’t provide any additional info. Maybe he’s doing db operations. Maybe he’s running something else on the server.
The traffic can be generally ok and then the OS is doing something weird or some other application is doing something weird that can affect kamailio for a short period of time. Then you have this extremely short bottlenecks and packets are dropped.
And it all depends on the testing environment: CPU, synch or asynch logging, etc.
One can stress kamailio on low performing hardware to reach the limit of a sistem faster and the results can be “misleading” for others that are used to test on server grade hardware.
In the end, we agree with each other and my feeling is that we are repeating the same concept.
Checking for dropped packets is always a good idea. How to deal with dropped packets depends a lot of the context.
In most of my deployments I don’t need to mess with the udp queue size.
For high cps traffic, from my experience, it’s a must.
And of course, going overboard and increasing it too much just makes things worse.
- ovidiu
> On Mar 23, 2024, at 7:29 PM, Ovidiu Sas via sr-users <sr-users@lists.kamailio.org> wrote:
>
> Because you have dropped packets.
> The queue it’s empty most of the time and if is full for a few milliseconds and that’s the moment when you experience dropped packets.
Totally fair. Just wondering if that's what we're discussing here. OP said he's running sipp, and sipp doesn't push out volatile workloads that are offset by periods of little to no activity to rapidly drain the queue.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: