Well it always really depends on what exactly you are doing. But in general, anything to do with RTP is going to be more CPU intensive. In general, signaling is very little traffic, and a well designed server can do most of it's operations from memory. You'll notice for a typical call, there is next to no signaling that occurs during the call (of course, depending on your implementation)<div>
<br class="webkit-block-placeholder"></div><div>With RTP, you have a constant stream of packets to sort out, and deal with. Of course, it also depends on what volumes you are talking about.. However I think all in all, RTP is always going to be expensive to work with. That's my $0.02</div>
<div><br class="webkit-block-placeholder"></div><div>-Brett</div><div><br><br><div class="gmail_quote">On Wed, Apr 1, 2009 at 9:25 PM, Alan Frisch <span dir="ltr"><<a href="mailto:frisch.alan@gmail.com">frisch.alan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Looking at deploying a test bed with a couple servers.<br>
<br>
Just wondering which is more CPU intensive... the server running<br>
OpenSIPS or the servers proxying the media (no codec translation)?<br>
<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>
</blockquote></div><br></div>