ahh yes, my bad.
Alex, thanks for drawing that to my attention.

On 3/09/2015 10:03 PM, Alexandru Csete wrote:
> On Thu, Sep 3, 2015 at 3:38 AM, glen english <[email protected]> wrote:
>> Nice work Alex
>>
>> For a lump of code to be using THAT much CPU, and these CPUs are very
>> capable something must be terribly wrong. maybe turn some of the
>> optimizations off and see what happens.  Can you break it down to
>> computation effort (something stuck in a loop, loop variable getting
>> trashed leading to excessive iterations)  or  cache thrashing  ?
>>
> Hi Glen,
>
> Just to be clear, the numbers I posted do not express CPU load like
> e.g. top or time does. Instead they show how much % of the application
> execution time is spent in various functions. That's why I didn't post
> any hardware details.
>
> The perf tool is developed by linux kernel devs and is available on
> any linux system with kernel 2.6 or later:
> https://perf.wiki.kernel.org/index.php/Main_Page
>
> It can do much more advanced profiling than what I posted (also at
> assembly level), but even in its simplest form it gives a good idea of
> where an application spends most time.
>
> Alex
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991


------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to