Comment 14 for bug 990992

Also, I don't really see why you use QThread::msleep(1) instead of just
increasing kPollIntervalMillis to 2 in controllermanager.cpp. We are
polling on a timer in our own poll thread. msleeping a callback in that
thread should be roughly identical to setting the polling interval higher.
Based on that reasoning it seems to make sense that by doing msleep(1) you
cut your CPU usage roughly in half since the poll frequency will roughly
halve

On Mon, May 21, 2012 at 2:27 PM, RJ Ryan <email address hidden> wrote:

> Can you give the load/idle numbers for no MIDI device enabled? (that way
> we see a baseline for no polling going on at all)
>
>
> On Mon, May 21, 2012 at 1:54 PM, Bill Good <email address hidden>wrote:
>
>> If someone whose system is noticeably heated by the unrestricted polling
>> can test this it'd be much appreciated, I'm in the process of moving
>> country so I just had enough time to write a fix and watch htop for a
>> few minutes.
>>
>> --
>> You received this bug notification because you are a member of Mixxx
>> Development Team, which is subscribed to Mixxx.
>> https://bugs.launchpad.net/bugs/990992
>>
>> Title:
>> The new controller polling frequency is too high for desktop systems
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/mixxx/+bug/990992/+subscriptions
>>
>
>