I am currently developing an audio layout using AWE Designer and have a question regarding CPU performance differences between the Win32 Native target and the actual Hexagon DSP hardware.
Observation:
When running the layout on the Win32 Native target, I noticed that the PC CPU usage for a single instance often hits 100% (showing an "Overflow" status), which suggests the CPU is overloaded.
However, when I run the same layout on the Hexagon DSP, the processing load is distributed evenly across multiple cores (e.g., CPU0 to CPU5), and the system runs smoothly without overflow.
My Question:
Is this behavior expected? I understand that the Win32 target might handle threading differently than the Hexagon architecture. Does a "CPU Overflow" on the Win32 Native target necessarily mean my audio algorithm is too complex, or is this simply a limitation of the single-threaded simulation on Windows compared to the multi-core parallel processing on the Hexagon DSP?
I want to make sure I am not overlooking a potential performance issue before finalizing the design.
Thank you for your clarification!