1. Community Forum
  2. AWE Designer
  3. Peak MHz profiling

Peak MHz profiling

6 posts / 0 new
Log in or register to post comments
Last post
Fri, 04/04/2025
5:28am
bohr_13977
#1
Top
#1
Peak MHz profiling

Hi,

There are both AWE Designer and AWE MATLAB API MHz profiling possibilities. However, it is the average MHz profiling I mostly get. The peak profiling is only mentioned as a total number for the entire layout in one place. It is the peak profiling that tells us if we have a problem.

Example: I have a layout that takes 15% average on target but takes 20% peak. How can I find out what module(s) causes the peak fluctuations? I prefer MATLAB API.

Kind regards,

BOHR

Fri, 04/04/2025
11:36am
DSPC_Gary
Top

Hi Bohr,

Start by seeing whether the information under "Module Profile Type" in this article is of use.  You will need to run several passes of profiling and then look to see which modules show the greatest variation.  Is this helpful?

https://tinyurl.com/2ffxbs95

Thanks,

Gary

Mon, 04/14/2025
6:51am
bohr_13977
Top
(Reply to #2)

Thanks for the reply and sorry for the long break Gary,

This peak profiling is only accessible from the AWE Designer layouts and not MATLAB API generated layouts, correct?

Is there then a way to convert a MATLAB API layout to AWE Designer layout to access this kind of profiling?

Regards,

BOHR

Tue, 04/15/2025
11:01am
DSPC_Gary
Top

Hi Bohr,

Please try using the following function (set_profiling_options) at the MATLAB console to enable peak profiling mode.

>> help set_profiling_options
  SUCCESS = set_profiling_options(instanceID, profilingOptions)
  Set the profiling options in an instance.
 
  Arguments: 
    instanceID - Instance ID in which to set the module profiling type.
 
    optionsMask  - Mask corresponding to the profiling option. Default to 
                   combined mask for all profiling options
    profilingOptions - value of profiling options. It can be a single or 
                       combination of the following options.
                       Bit 0 value of 0x0 - Average profiling on modules (default)
                       Bit 0 value of 0x1 - Peak profiling on modules
                       Bit 1 value of 0x0 - Enable accurate profiling (default)
                       Bit 1 value of 0x1 - Disable accurate profiling

It is not possible to convert a layout done via MATLAB scripting directly to an AWD.

Let me know if this works for you.

Thanks,

Gary

Wed, 06/04/2025
8:11am
bohr_13977
Top
(Reply to #4)

Hi Gary, sorry for the long delay, I was busy with other things.

What is an instance ID and how do I get it via MATLAB API for my layout or any other part of the layout?

How to set the optionsMask?

I assume I can use get_profiling_options to read the current values. However, the help file says:

profilingOptions = get_profiling_options(instanceID)
   Get the current profiling options in an instance. On SUCCESS, status will 
   be 1 and on failure it will be 0.

If it returns 0 is it then the profiling options or does it mean failure?

Kind regards,

BOHR

Wed, 06/04/2025
12:35pm
DSPC_Gary
Top

Hi Bohr,

Different Instance Ids are associated with implementations that have more than one AWECore running on the SoC.

See:  Multi-Instance AWE Core Integration Guide

Using the Native mode as an example, see in AWE Server that this supports 4 Instances, 0, 1, 2, 3.  

In the layout, the InstanceID is shown under the Module as highlighted.  Use the Change Thread module to change between instances in a single layout.

Regarding accessing the Instance ID of a module via MATLAB, use the "coreID" property:

Regarding setting profiling options, the actual calling sequence is:

function SUCCESS = set_profiling_options(instanceID, optionsMask, profilingOptions)

Regarding the MATLAB function get_profiling_options(), it has multiple return values, as shown:

function [profilingOptions, status] = get_profiling_options(instanceID)

Here's a code snippet demonstrating their use:

        [profilingOptions, status] = get_profiling_options();

        verifyEqual(testCase, status, 1);

        verifyEqual(testCase, profilingOptions, 0); % 0x0 | (0x0 << 1)

 

Thanks, Gary