hi,<br><br>is a blade hp server which is works with external disk(they are connected with optical line.) BUT because for the blade I'm working in there is no space in that disk so I'm working in local disk which is pata technology!!! very old and slow IO.<br>
Does anyone knows hot to define a htable in kamailio.cfg. I included details in my previous email<br><br>Thanks<br>Alex<br><br><br><br><div class="gmail_quote">On Thu, Dec 24, 2009 at 2:02 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On 12/24/2009 06:59 AM, Henning Westerholt wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, December 23, 2009 9:52 am, alex pappas wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In the server I'm running Kamailio I have a good CPU(4 cores) and 2G<br>
memory but for reading or writing to the disk i have a big problem.Is a<br>
blade server with very bad disk which they do also software raid 1. Even<br>
if I try to write in the log file of kamailio I get such a high load<br>
that I cannot pass the 10 CPS.<br>
</blockquote>
<br>
Hey Alex,<br>
<br>
ok, this is indeed a really bad disk. :) Regarding the slow logging, you<br>
could check the syslog configuration if its configured to write<br>
asynchronously (there should be a "-" in front of the log statement in<br>
syslog.conf). And also check if you perhaps not use a to high log level in<br>
the kamailio cfg.<br>
</blockquote>
<br></div></div>
Oh, so that's what the '-' does. Thanks Henning, one learns something new every day from you. :-)<br>
<br>
Alex - this server is not a Dell Poweredge 2850/2950 with a PERC 5i, is it? I have run into a bug on a few of these where I/O causes enormous blocking/waiting, and discovered it by turning off syslogging and watching the 'waiting' portion of the load to go down. It was necessary to replace the defective PERC to fix the problem.<div class="im">
<br>
<br>
-- <br>
Alex Balashov - Principal<br>
Evariste Systems<br>
Web : <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a><br>
Tel : (+1) (678) 954-0670<br>
Direct : (+1) (678) 954-0671<br>
<br></div><div><div></div><div class="h5">
_______________________________________________<br>
Kamailio (OpenSER) - Users mailing list<br>
<a href="mailto:Users@lists.kamailio.org" target="_blank">Users@lists.kamailio.org</a><br>
<a href="http://lists.kamailio.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.kamailio.org/cgi-bin/mailman/listinfo/users</a><br>
<a href="http://lists.openser-project.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser-project.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>