<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Russell Bryant wrote:
<blockquote cite="mid474598AE.1050905@digium.com" type="cite">
<pre wrap="">Klaus Darilion wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Just as clarification: Asterisk can handle only 8.5 call setup requests
per second on this powerful hardware?
</pre>
</blockquote>
<pre wrap=""><!---->
Let me note that I do find this number to be disturbingly low. We will
definitely be doing some work to determine bottlenecks and get this improved
very soon. Steve Murphy is already in the process of converting a lot of the
key data structure management in chan_sip to use astobj2, which I believe will
help this out a lot.
Another issue is that there is only one thread for handling incoming SIP
requests, so the fact that it is dual core doesn't help. But, that's not something that is about to change soon.</pre>
</blockquote>
<br>
IMO it is not too difficult to change... Create pool of threads pool
waiting on queue.<br>
the main sip thread will read the sip packet from the socket and add it
to the queue<br>
and raise a condition variable signalling packet arrival.<br>
<br>
The first worker thread sleeping on condition will awaken wnd will get
the packet from the queue<br>
and will handle it.<br>
<br>
Thanks<br>
Vadim<br>
<blockquote cite="mid474598AE.1050905@digium.com" type="cite">
<pre wrap=""> Also, Asterisk does start a thread for
every new call, which can be rather expensive.
</pre>
</blockquote>
<br>
</body>
</html>