Waveforms needs some optimization/caching
Bug #1194456 reported by
xorik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Hi all!
I think mixxx need to optimize waveform display code, beacuse it uses many percents of CPU at now.
I have Intel(R) Celeron(R) CPU E3400 @ 2.60GHz GenuineIntel and x86_64 gentoo linux. I'm use "top" in terminal for measuring CPU percents.
I load 2 tracks into decks and paused them and set waveform FPS limit to 30
Empty waveform: 18% CPU
Filtered - Qt: 57% CPU
HSV: 45% CPU
If I increase FPS limit, the numbers will be much bigger (70-80% CPU for HSV and filtered waveform).
I think this is because of many calculations, while drawing waveform, without caching. I thing caching isn't hard to code, but saves many CPU percents (and battery life) when mixing.
Changed in mixxx: | |
status: | New → Confirmed |
tags: | removed: cache cpu optimization |
To post a comment you must log in.
I agree that there is much space for Improvements. But I do not agree that caching isn't hard to code.
We have already a blueprint for this. /blueprints. launchpad. net/mixxx/ +spec/tiling- waveform
https:/
If you want to adopt parts of this issue, a first step is to create a new page at www.mixxx.org/wiki link it to the blueprint and outline your ideas there.
I have currently a waveform dejerk branch in progress with also some CPU savings.
Filtered Qt and HSV are not well optimized. What are your results of the GL waveforms?
An other first step: you could make a pure GL HSV version.