<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 14-01-24 11:16 AM, Amit wrote:<br>
</div>
<blockquote cite="mid:52E283C0.7070003@avhan.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font color="#000000" face="Calibri"><br>
If I assume that Asterisk will write data on disk every second
for each call, I will need disk array to support minimum of 500
IOPS. Where as if Asterisk push data every 2 seconds, I can deal
with array supporting 250 IOPS. <br>
But if I assume that Asterisk will write data on disk for every
RTP packet received, as and when received, I will need disk IO
system with approx 25000 IOPS assuming 20 ms RTP packet.</font><br>
</blockquote>
<font face="Calibri">You're assuming that asterisk will perform an
fsync() after each write. If asterisk writes without an fsync
after each write, then the OS will schedule writes intelligently
based on RAM/disk IO available rather than scheduling each one as
a separate write.<br>
<br>
Looking at the code for ast_writestream() there doesn't appear to
be an fsync() type call after each write, but someone more
familiar with the internals of Asterisk would be better able to
verify that.<br>
<br>
</font>
<pre class="moz-signature" cols="72">--
Looking for (employment|contract) work in the
Internet industry, preferably working remotely.
Building / Supporting the net since 2400 baud was
the hot thing. Ask for a resume! <a class="moz-txt-link-abbreviated" href="mailto:ispbuilder@gmail.com">ispbuilder@gmail.com</a></pre>
</body>
</html>