View Revisions: Issue #7501

Summary 0007501: Increased DSP load with master/6.0-preX compared to 5.12
Revision 2017-11-04 12:11 by timbyr
Description I realize that work on the master branch is a work in progress but I have noticed an increase in the DSP values with the same session using optimized builds of 5.12 and master(f7bca32a).

A simple session with 27 audio tracks I see a DSP value of about 8% in 5.12 and 18% in master with optimized builds using a buffer size of 512 samples.

While the increase may be necessary to enable new functionality or a result of unfinished changes etc others will notice the increase, so this issue is intended to track any relevant changes.

Two changes I'm aware of in master that are having an effect:

- Resampling is now occurring in AudioPort::cycle_start/end using a separate thread pool to the process threads.

- There is now a DelayLine in each Route that increases processing and is (as yet) not optimized [ Now optimized - see below ]

I'm attaching a pair of traces(for use with chrome/ium://tracing) that shows the difference that the resampling makes to the timing of AudioEngine::process_callback
Revision 2017-11-03 12:08 by timbyr
Description I realize that work on the master branch is a work in progress but I have noticed an increase in the DSP values with the same session using optimized builds of 5.12 and master(f7bca32a).

A simple session with 27 audio tracks I see a DSP value of about 8% in 5.12 and 18% in master with optimized builds using a buffer size of 512 samples.

While the increase may be necessary to enable new functionality or a result of unfinished changes etc others will notice the increase, so this issue is intended to track any relevant changes.

Two changes I'm aware of in master that are having an effect:

- Resampling is now occurring in AudioPort::cycle_start/end using a separate thread pool to the process threads.

- There is now a DelayLine in each Route that increases processing and is (as yet) not optimized.

I'm attaching a pair of traces(for use with chrome/ium://tracing) that shows the difference that the resampling makes to the timing of AudioEngine::process_callback
Revision 2017-11-03 12:04 by timbyr
Description I realize that work on the master branch is a work in progress but I have noticed an increase in the DSP values with the same session using optimized builds of 5.12 and master(f7bca32a). With the same 27 track audio session I see a DSP value of about 8% in 5.12 and 18% in master with optimized builds using a buffer size of 512 samples.

While the increase may be necessary to enable new functionality or a result of unfinished changed etc others will notice the increase, so this issue is intended to track any relevant changes.

Two changes I'm aware of in master that are having an effect:

- Resampling is now occurring in AudioPort::cycle_start/end using a separate thread pool to the process threads.

- There is now a DelayLine in each Route that increases processing and is (as yet) not optimized.

I'm attaching a pair of traces(for use with chrome/ium://tracing) that shows the difference that the resampling makes to the timing of AudioEngine::process_callback