Hi guys,<br><br>You were right! shutting down syslog logging resulted in clean successful tests. I still don't have the fix for this, but will post it here when I do.<br><br>Thanks!<br><br>Alejandro.<br><br><div class="gmail_quote">
2011/9/14 Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<u></u>
<div bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
Please check, as Brett said, if your logging is not the issue - if
syslog is in async mode.<br>
Further more, if logging turns out not to be the problem, you could
use the time threshold parameters from the core for DNS and overall
message processing [1], or the time threshold in the DB_MYSQL
module, for queries [2], to check if DNS or MySQL is causing this
performance issues.<br>
<br>
[1] <a href="http://www.opensips.org/Resources/DocsCoreFcn#toc49" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn#toc49</a><br>
[2]
<a href="http://www.opensips.org/html/docs/modules/devel/db_mysql.html#id249058" target="_blank">http://www.opensips.org/html/docs/modules/devel/db_mysql.html#id249058</a><br>
<br>
Regards,<br>
<pre cols="72">Vlad Paiu
OpenSIPS Developer</pre><div><div></div><div class="h5">
<br>
On 09/14/2011 03:55 AM, Brett Nemeroff wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5">2011/9/13 Alejandro Ríos <span dir="ltr"><<a href="mailto:alerios@debian.org" target="_blank">alerios@debian.org</a>></span><br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
Hi all,<br>
<br>
I'm running a sipp load test to an opensips instance on a 16
core, 8GB ram blade server. It's only 100 simultaneous calls,
at 10 calls per second, and I'm getting lots of
retransmissions from the sipp UAC.<br>
</blockquote>
<div><br>
I'll give you the same advice I gave someone else just a sec
ago. Check your syslog config and see if you are set up for
async writes. Turn logging off completely on opensips and see
if that changes anything. I've seen bad logging configs bring
perfectly capable systems to it's knees.<br>
-Brett<br>
<br>
</div>
</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>