I noticed that most of my projects and the demo seem to be using a few percent more CPU after the update to 11.0.39. It appears to be about a 3-5% increase.
This is specific to Ubuntu 19.10 so far. I have yet to do the update on my Windows 10 machine.
11.0.39 is using considerably more CPU
-
- KVRist
- Topic Starter
- 68 posts since 26 Nov, 2011
After letting my Ubuntu machine run for hours using the identical "Static Observer" test I have to say that there is a noticeable increase in CPU usage. In fact I would say that while the CPU meter in WF11 shows 5% or more of an increase the actual increase shown on the Ubuntu System Monitor is even higher. The system is running stable, but actually hotter using either the software or OpenGL rendering options with no other applications running.
I will run similar tests on my Windows box but it has so much horsepower it doesn't really matter. Nevertheless, one of the key strengths of Waveform is it's efficiency. I think we lost a bit with this version - at least the Linux build.
I will run similar tests on my Windows box but it has so much horsepower it doesn't really matter. Nevertheless, one of the key strengths of Waveform is it's efficiency. I think we lost a bit with this version - at least the Linux build.
-
- KVRist
- Topic Starter
- 68 posts since 26 Nov, 2011
UPDATE: Performed the update from 11.0.26 to 11.0.39 on my Win10 machine and a similar efficiency loss appears. On that machine the "Static Observer" demo project used between 3 and 6% CPU on the WF11 CPU meter prior to the update. Now with 11.0.39, the very same project uses between 6 and 18% CPU!, more than double the previous load!
What's up Tracktion?
Is this update really supposed to hit the CPU that much harder for a good reason?
What's up Tracktion?
Is this update really supposed to hit the CPU that much harder for a good reason?
Last edited by ScottAxxe on Sat Jun 13, 2020 12:59 pm, edited 1 time in total.
-
- KVRian
- 1300 posts since 3 May, 2005 from Victoria, BC
I think .39 enables plugin sandboxing by default. Are both your tests running with/without sandboxing?
-
- KVRist
- Topic Starter
- 68 posts since 26 Nov, 2011
On the Ubuntu machine turning off Sandboxing makes no difference to CPU load that I can see. It's still the same increase from 11.0.26. The 64 bit mixing option is also off but it was off by default to begin with.
On the Windows box, turning off sandboxing was equally ineffective at moderating the new CPU usage increase. On the Windows machine the demo that would peak at 6-7% running 11.0.26 now actually hits as high as 18%!
In both cases I closed Waveform and relaunched after changing the sandboxing option.
So, at this point I have to deduce that a common change to the engine has caused Linux and Windows versions to increase their CPU usage by a substantial amount. I can only assume the Mac version as well. I haven't installed yet on my Mac Mini as I don't really intend on running on that machine and I'd rather not use up the last of my three installs on that.
In my mind I have been fairly thorough at controlling my variables in these tests. I changed the thread title to reflect my confidence in these results. On both platforms, the CPU usage has increased quite substantially. The Linux machine actually runs noticeably warmer.
This is NOT the kind of change users want to see in a DAW when a new revision comes out. I'm really learning to like Waveform 11 but this latest update is a setback in my opinion.
I hope we hear some feedback from Tracktion on this.
If this is the "new normal" (I hate that phrase) for Waveform, at least let us know why.
On the Windows box, turning off sandboxing was equally ineffective at moderating the new CPU usage increase. On the Windows machine the demo that would peak at 6-7% running 11.0.26 now actually hits as high as 18%!
In both cases I closed Waveform and relaunched after changing the sandboxing option.
So, at this point I have to deduce that a common change to the engine has caused Linux and Windows versions to increase their CPU usage by a substantial amount. I can only assume the Mac version as well. I haven't installed yet on my Mac Mini as I don't really intend on running on that machine and I'd rather not use up the last of my three installs on that.
In my mind I have been fairly thorough at controlling my variables in these tests. I changed the thread title to reflect my confidence in these results. On both platforms, the CPU usage has increased quite substantially. The Linux machine actually runs noticeably warmer.
This is NOT the kind of change users want to see in a DAW when a new revision comes out. I'm really learning to like Waveform 11 but this latest update is a setback in my opinion.
I hope we hear some feedback from Tracktion on this.
If this is the "new normal" (I hate that phrase) for Waveform, at least let us know why.
-
- KVRAF
- 1603 posts since 9 Jan, 2018
FigBug is with Tracktion.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRian
- 1300 posts since 3 May, 2005 from Victoria, BC
We aren't aware of any changes that should have caused a decrease in performance. We are going to try and track down the exact version where it happened and see if we can figure out the cause.
-
- KVRist
- Topic Starter
- 68 posts since 26 Nov, 2011
Awesome! Thanks. It's a great DAW and I'm liking it more all the time. I was just disappointed to see the loss in performance.
Like I said I simply ran the Static Observer Rorschach Litany demo with both 11.0.26 and 11.0.39. Being a newb to Waveform that demo has become a benchmark for me to mess with as I'm learning. It also sounds cool.
In any case, I cannot configure 11.0.39 with any of the new options and obtain the same level of efficiency I observed with 11.0.26. I am a developer so I believe I compared apples to apples as much as possible.
Let me know if you want me to try anything specific on my installs.
Like I said I simply ran the Static Observer Rorschach Litany demo with both 11.0.26 and 11.0.39. Being a newb to Waveform that demo has become a benchmark for me to mess with as I'm learning. It also sounds cool.
In any case, I cannot configure 11.0.39 with any of the new options and obtain the same level of efficiency I observed with 11.0.26. I am a developer so I believe I compared apples to apples as much as possible.
Let me know if you want me to try anything specific on my installs.
-
- KVRist
- 166 posts since 9 Nov, 2012
I have had to disable sandboxing, it continuously blocked Waveform, it is to disable sandboxing and work correctly. And if it were not enough it consumes much more with the enabled one.