[ GUIDA ] Differenze tra i vari governor

[stevtec86]

Qualcuno sa le differenze tra questi governor e magari abbinati a quale I/O ( se sono piu meno aggressivi di altri, come si comporta etc etc): Abyssplug, pegasusq e intellimand?

[illuminato67]

Su PegasusQ segnalo questa: https://www.androidiani.com/forum/mo...-governor.html

[illuminato67]

Avete visto il nuovo governor LulzactiveQ (prerogativa del Siyah 4.1.2) ?


Il "creatore" scrive su XDA:
http://forum.xda-developers.com/show...php?p=30839989
LulzactiveQ

I was decided to optimize Lulzactive governor by including the dec_cpu_load parameter.

----
I was going to put it because if the inc_cpu_load is setted at a high value (example: 90%) and the pump_down_steps is also setted high (2 or 3 steps down if load < inc_cpu_load) it would happen a problem:

Suppose the current load is between 80 and 89% all the sampling rate and the pum_down_steps is 2 or 3. Do you think is a good idea to go down 2/3 steps in the load at that high?

This is not a theorical issue, i really felt lag when playing some simple games and my conclusion was that situation was happening in that moment.

Thats why i created dec_cpu_load, in this way we can tell the governor exactly when go down pump_down_steps.
----

I also fixed a little bug as well that the up_sample_time and down_sample_time wasnt been respected (the governor was scaling up and down as soon as the load criteria was matched).
-----

And i added as gokhan requested, the hotplug parameters from pegasusq. So now we have to governors with hotplug queue logic.

To the hotplug part i had to create another sample rate. The name is hotplug_sample_rate. I created that to make the hotplug part completely independent from scale up / down frequencies part. In fact, they are running in different threads.
-----

That's it. I also putted some logs that can be enabled / disabled by the dvfs_debug parameter.
If do you think something was wrong, or a problem apperead please enable this parameter for a while and execute this command in terminal emulator or adb:

dmesg > /sdcard/lulzactiveq.log.txt
----------------------

This is only a battery profile suggestion for the 16 steps. Please explore it!!!!!!

-- Parâmetros Lulzactive
echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "40" > /sys/devices/system/cpu/cpufreq/lulzactive/dec_cpu_load
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/*******_step
echo "2" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "25000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "14" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
-- Lulzactive - Hotplug Queue parameters
echo "50000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_sample_rate
echo "13" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_up_rate
echo "13" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_down_rate
echo "600000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_0
echo "350" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_1_1
echo "300" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_0
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock
-- debug on/off
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/dvfs_debug



I want to thank a lot Gokhan for the help he gave me to do this job!!!


Inviato con il mio S2 CM10/Siyah 4.1.1
Settaggi di illuminato67: https://www.androidiani.com/forum/sh....php?p=1826983

[alegu]

Avete visto il nuovo governor LulzactiveQ (prerogativa del Siyah 4.1.2) ?


Il "creatore" scrive su XDA:
http://forum.xda-developers.com/show...php?p=30839989
LulzactiveQ

I was decided to optimize Lulzactive governor by including the dec_cpu_load parameter.

----
I was going to put it because if the inc_cpu_load is setted at a high value (example: 90%) and the pump_down_steps is also setted high (2 or 3 steps down if load < inc_cpu_load) it would happen a problem:

Suppose the current load is between 80 and 89% all the sampling rate and the pum_down_steps is 2 or 3. Do you think is a good idea to go down 2/3 steps in the load at that high?

This is not a theorical issue, i really felt lag when playing some simple games and my conclusion was that situation was happening in that moment.

Thats why i created dec_cpu_load, in this way we can tell the governor exactly when go down pump_down_steps.
----

I also fixed a little bug as well that the up_sample_time and down_sample_time wasnt been respected (the governor was scaling up and down as soon as the load criteria was matched).
-----

And i added as gokhan requested, the hotplug parameters from pegasusq. So now we have to governors with hotplug queue logic.

To the hotplug part i had to create another sample rate. The name is hotplug_sample_rate. I created that to make the hotplug part completely independent from scale up / down frequencies part. In fact, they are running in different threads.
-----

That's it. I also putted some logs that can be enabled / disabled by the dvfs_debug parameter.
If do you think something was wrong, or a problem apperead please enable this parameter for a while and execute this command in terminal emulator or adb:

dmesg > /sdcard/lulzactiveq.log.txt
----------------------

This is only a battery profile suggestion for the 16 steps. Please explore it!!!!!!

-- Parâmetros Lulzactive
echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "40" > /sys/devices/system/cpu/cpufreq/lulzactive/dec_cpu_load
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/*******_step
echo "2" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "25000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "14" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
-- Lulzactive - Hotplug Queue parameters
echo "50000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_sample_rate
echo "13" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_up_rate
echo "13" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_down_rate
echo "600000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_0
echo "350" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_1_1
echo "300" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_0
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock
-- debug on/off
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/dvfs_debug



I want to thank a lot Gokhan for the help he gave me to do this job!!!


Inviato con il mio S2 CM10/Siyah 4.1.1
Settaggi di illuminato67: https://www.androidiani.com/forum/sh....php?p=1826983

Si ma lui li mette a disposizione ma a chi lo fa provare...alla moglie... a parte gli scherzi...com'e'... Nel senso va bene?!?!?

"DORI5.69+S3rom4.0.4xwlpt+XXLQ6"-
»»»»»»»»>>>>>>o<<<<<<««««««««

[illuminato67]

Si ma lui li mette a disposizione ma a chi lo fa provare...alla moglie... a parte gli scherzi...com'e'... Nel senso va bene?!?!?

"DORI5.69+S3rom4.0.4xwlpt+XXLQ6"-
»»»»»»»»>>>>>>o<<<<<<««««««««

Ale, per ora non è ottimizzato.
Ci stanno lavorando

Inviato con il mio S2 CM10/Siyah 4.1.2
Settaggi di illuminato67: https://www.androidiani.com/forum/sh....php?p=1826983

[alegu]

Ale, per ora non è ottimizzato.
Ci stanno lavorando

Inviato con il mio S2 CM10/Siyah 4.1.2
Settaggi di illuminato67: https://www.androidiani.com/forum/sh....php?p=1826983

Non e' riferito solo a Gohan ma anche agli altri kernelisti senno' sembro di parte anche se personalmente chiunque puo' fare qualunque ovviamente...ma prima di far uscire qualcosa di nuovo non potrebbero testarlo come si deve e poi farle uscire queste novita'?!?!? Mi sembra che buttano fuori e poi ritirano indietro per macrocavolate... Fossero micro... A volte non funziona praticamente nulla... Freeze immediati, riavvii ecc. Riflessione... Comunque mi sto avvicinando a quello che dice Rox77... Sto testando tutto a manetta (col Dori) governor compresi senno' sarei offtopic ed effettivamente le differenze sono poche... Ma sono in test e magari mi sbaglio...

"DORI5.69+S3rom4.0.4xwlpt+M250S"-
IMPOSTAZIONI KERNEL IN CWM DORIMANX 5.69

[illuminato67]

Non e' riferito solo a Gohan ma anche agli altri kernelisti senno' sembro di parte anche se personalmente chiunque puo' fare qualunque ovviamente...ma prima di far uscire qualcosa di nuovo non potrebbero testarlo come si deve e poi farle uscire queste novita'?!?!? Mi sembra che buttano fuori e poi ritirano indietro per macrocavolate... Fossero micro... A volte non funziona praticamente nulla... Freeze immediati, riavvii ecc. Riflessione... Comunque mi sto avvicinando a quello che dice Rox77... Sto testando tutto a manetta (col Dori) governor compresi senno' sarei offtopic ed effettivamente le differenze sono poche... Ma sono in test e magari mi sbaglio...

"DORI5.69+S3rom4.0.4xwlpt+M250S"-
IMPOSTAZIONI KERNEL IN CWM DORIMANX 5.69

Mi piace la tua nuova "apertura mentale", indice di sincera passione per il modding sperimentale e scientifico.
Ciao Ale

Inviato con il mio S2 CM10/Siyah 4.1.2
Settaggi di illuminato67: https://www.androidiani.com/forum/sh....php?p=1826983

[danielhouse90]

qualche configurazione per lo SmartassV2 per risparmiare batteria su custom rom e siyah kernel?

[illuminato67]

qualche configurazione per lo SmartassV2 per risparmiare batteria su custom rom e siyah kernel?

Se non sbaglio lo stava provando Leo. Puoi chiedere a lui

Inviato con il mio S2 CM10/Siyah 4.1.2
Settaggi di illuminato67: https://www.androidiani.com/forum/sh....php?p=1826983

[danielhouse90]

Se non sbaglio lo stava provando Leo. Puoi chiedere a lui

Inviato con il mio S2 CM10/Siyah 4.1.2
Settaggi di illuminato67: [GUIDA][EXTWEAKS]imparare a usare i settaggi - Pagina 13 - Forum Android Italiano

leo chi scusa?