<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.5730.11" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>> In fact, the amount of time it takes to fetch memory from a cache miss
<BR>> can easily ruin the single element lookup performance in a look up
<BR>> table.<BR></DIV>
<DIV><FONT face=Arial size=2>That's a good observation I hadn't
considered. No, none of the CPUs I work with cache anything other than the
next few instructions. But, like you say, that isn't true of just about
any CPU Asterisk is likely to be run on. It used to be that code
optimization was fairly straightforward. But between caches and pipelines
and multiple execution units, etc. It is becoming a very complex science of its
own, and as Benny stated, often very CPU (or even main board)
dependent.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I guess the bottom line here was the comment about
1.4 X 0 is 0. These two codecs don't contribute significantly to CPU
utilization any way they are used.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Wilton</FONT></DIV>
<DIV> </DIV></BODY></HTML>