hi all
i noticed, that the cpu frequency scaling doesn't react on cpu load caused by pd. even if i have a constant high load - for instance when running several hundred [osc~]s - the cpu frequency stays at the lowest value of 800 MHz. i need to run another program, such as 'yes' or 'burnMMX' in order to trigger the scaling to set the frequency to the maximum of 2401000 MHz. so far i only noticed this behaviour with pd. other programs don't seem to 'fool' frequency scaling.
specs: pd 0.41.4 running in -rt -jack mode 2.6.24-21-rt (from ubuntu hardy) Intel Core 2 Duo CPU T8300 @ 2.40GHz scaling_governor: on_demand (default)
i know, that it is most likely not a direct pd problem, but probably some other pd-linux users encountered a similar behaviour. as a workaround, i currently manually switch the scaling_governor to 'performance', when i am in a 'performative' situation. i wonder, if there is a real fix for that problem.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
hello,
Roman Haefeli a écrit :
hi all
i noticed, that the cpu frequency scaling doesn't react on cpu load caused by pd.
this is strange. did you try without -rt or -jack?
here it works as expected, but i always switch to performance mode anyway since frequency scaling is quite slow and can lead to audio click for a second when you switch on your patch, before the CPU frequency go to maximum.
So, i think that switching to performance mode when you need performance is not really a fix or a workaround : it's the way to go.
Cyrille
even if i have a constant high load - for instance when running several hundred [osc~]s - the cpu frequency stays at the lowest value of 800 MHz. i need to run another program, such as 'yes' or 'burnMMX' in order to trigger the scaling to set the frequency to the maximum of 2401000 MHz. so far i only noticed this behaviour with pd. other programs don't seem to 'fool' frequency scaling.
specs: pd 0.41.4 running in -rt -jack mode 2.6.24-21-rt (from ubuntu hardy) Intel Core 2 Duo CPU T8300 @ 2.40GHz scaling_governor: on_demand (default)
i know, that it is most likely not a direct pd problem, but probably some other pd-linux users encountered a similar behaviour. as a workaround, i currently manually switch the scaling_governor to 'performance', when i am in a 'performative' situation. i wonder, if there is a real fix for that problem.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sun, 2008-11-02 at 13:13 +0100, cyrille henry wrote:
hello,
Roman Haefeli a écrit :
hi all
i noticed, that the cpu frequency scaling doesn't react on cpu load caused by pd.
this is strange. did you try without -rt or -jack?
yes, i tried now. only when running pd -rt (no matter, if with -jack or with -alsa), it stops scaling from working. probably the process, that controls scaling, has lower priority?
here it works as expected, but i always switch to performance mode anyway since frequency scaling is quite slow and can lead to audio click for a second when you switch on your patch, before the CPU frequency go to maximum.
i see
So, i think that switching to performance mode when you need performance is not really a fix or a workaround : it's the way to go.
ok. thanks. do you use a script for that? if you already have one at hand, would you mind sharing it? otherwise i write my own.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
no. i don't have any script. but i've got a much better solution.
do : sudo dpkg-reconfigure gnome-applets then left click on the applet...
c
Roman Haefeli a écrit :
On Sun, 2008-11-02 at 13:13 +0100, cyrille henry wrote:
hello,
Roman Haefeli a écrit :
hi all
i noticed, that the cpu frequency scaling doesn't react on cpu load caused by pd.
this is strange. did you try without -rt or -jack?
yes, i tried now. only when running pd -rt (no matter, if with -jack or with -alsa), it stops scaling from working. probably the process, that controls scaling, has lower priority?
here it works as expected, but i always switch to performance mode anyway since frequency scaling is quite slow and can lead to audio click for a second when you switch on your patch, before the CPU frequency go to maximum.
i see
So, i think that switching to performance mode when you need performance is not really a fix or a workaround : it's the way to go.
ok. thanks. do you use a script for that? if you already have one at hand, would you mind sharing it? otherwise i write my own.
roman
___________________________________________________________ Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
cyrille henry -
Roman Haefeli