[SR-Users] Re: low performance with no apparent reason

We can agree on that, at least. :-) I'm not sure how far this bottle metaphor works, because water falls into the bottle at a constant rate and at a constant acceleration (force of gravity), notwithstanding the moderating effect of funnel shape or other geometric irregularities. I think in the real world, we are dealing with a situation where water falls into the bottle (through the bottle?) at different speeds, so most limits are related to that flow and not to funnel or bottle size. Or to say it differently: under most typical Kamailio workloads, which are I/O-bound, a single Kamailio process (bottle) can handle a certain amount of messages per second. You can't really make it handle more messages than it does without tweaking the nature of the workload. Assuming the workload is held constant, the only way to get more messages through the system is to have more worker processes, or bottles if you like, which has its own performance implications and limits (locking and CPU contention). Consequently, there's a certain throughput-maximising amount of bottles for a given workload that is neither so low as to under-utilise available resources, nor so high as to degrade the overall throughput from fighting for CPU, big locks over shared resources, overwhelming I/O dependencies (e.g. databases with queries), etc. The main input variable is the number of bottles itself. The size of the funnel isn't really relevant. If there are enough bottles and water goes into them at sufficient velocity, bigger funnels won't help. If the velocity is not sufficient or there aren't enough bottles, funnels of any size will just back up and overflow. About the only scenario where the funnel matters is the one you pointed out previously, where the inflow is highly irregular, is modally moderate, and only momentarily bursts to high volumes. -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800