Notwithstanding the fact that not all operations work in async routes, I would 
be curious to know why distributing the workload into a pool of async workers 
is "still a bottleneck of sorts". Are there architectural reasons for this that 
I am failing to consider? 

Also: I use set_dlg_profile(), but not in 'async' routes per se; instead, I 
suspend TM transactions and push them over an 'mqueue' into 'rtimer' processes. 
This appears to work fine.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Kamailio (SER) - Development Mailing List

Reply via email to