Trauma

Members
  • Content Count

    12
  • Joined

  • Last visited

  • Days Won

    5

Trauma last won the day on October 3

Trauma had the most liked content!

Community Reputation

12 Good

About Trauma

  • Rank
    Newbie
  1. Netdata is effectively a good too monitor your server. About "phys,phys,phys,virt,virt,virt,virt", seems like it's actually displayed/ordered like this. I also doubt HT core could be higher than physical cores. It's also possible that DSM kernel / drivers are missing something to handle this right (maybe bromowl kernel is working). About "load profil", isn't the readme clear enough ? Do you understand "loadaverage" thing ?
  2. Yes it seems like ! It certainly means acpi-cpufreq is not able to control threaded cores. You could use this simple loop to monitor cpu frequency, quick and dirty but works... (CTRL+C to escape): while true; do cat $(ls /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq); done
  3. Please try this version of the script, and report us if it's OK... or not please : https://raw.githubusercontent.com/Trauma/cpufreq-userspace-scaler/ht-compat/scaler.sh
  4. If you want, you can use variables to adjust speed and steps according to you're load profil. acpi-cpufreq driver gather frequencies from ACPI tables, so it's certainly related to your bios ACPI implementation. Try to tweak cpu and acpi settings in bios, it may help. Maybe this CPU is not completly supported on this mobo (bios update ?). Try this, to see if it's more consistant : cat /sys/devices/system/cpu/cpufreq/policy0/bios_limit Obviously not ! Anyway I'm not sure cpuinfo is totally reliable here. Prefer sysfs informations in my opinion. Try this, to see if it's more consistant : cat $(ls /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq) Please try this as well and report the output of the command here please (for your cpu it should return "8") : cat /proc/cpuinfo | grep cores | sort -u | awk '{ print $4 }'
  5. Thanks ! Not 100% sure about this but i guess boost frequency is managed by intel_pstate, which seems to be enabled in the kernel, but the default cpu frequency driver is set to cpu_freq. I did not succeed to make it work on my rig. I've tried intel_pstate=enable in the grub cmd_line, but no luck. I've also tried to load a compiled module, and it don't load. I guess some guys here have proven it's actually working, while benchmarking the NAS with turbo boost enabled or disabled in bios (they use geekbench in a docker container I guess).
  6. Long answer : Your CPU don not have only 3 modes, synology kernel for DS918+ provides only three cpufreq governors : powersave > set the cpu to its minimal freq performance > set the cpu to its maximal freq userspace > allow you to specify the desired frequency. This script use this governor to modulate the frequency according to system load (that's basically whats explained in the README). Short answer : no need to "modify some text", just RTFM
  7. Installation in rc.d will not work since this script do not provide start and stop args. As @Olegin spotted you can launch it form the task manager, that's the way i use it. Installation example (from your nas cli) : sudo curl https://raw.githubusercontent.com/Trauma/cpufreq-userspace-scaler/master/scaler.sh -o /usr/local/bin/scaler.sh && sudo chmod +x /usr/local/bin/scaler.sh Then run it through a startup triggered task, as root, in your DSM, with the following command : /usr/local/bin/scaler.sh & or with parameters : lowload=100 highload=200 scalingmaxfreq=2000000 scalingminfreq=1500000 /usr/local/bin/scaler.sh &
  8. This could maybe help you guys :
  9. I guess some off you could be intersted in this :
  10. Hi, Since I was not yet able to build a working cpufreq_ondemand.ko to allow automatic frequency scaling for JUN's loader 1.04b (DSM 6.2.2-24922 Update 2), i've written this script to allow dynamic CPU frequency scaling. It's hosted here : https://github.com/Trauma/cpufreq-userspace-scaler # cpufreq-userspace-scaler ##### Cpu frequency scaling script for cpufreq userspace governor ## If you're missing ondemand or conservative governors, this script is for you. This script is scaling cpu frequency according to current average load. You can set 3 frequency steps : low, mid, high. This 3 thresholds will automatically set cpu frequency accordingly : - the `lowload` threshold will set the cpu to his minimal frequency, unless you force it to `scalingminfreq` - the `midload` threshold will set the cpu to approximate mid range cpu frequency - the `highload` threshold will set the cpu to his maximal frequency, unless you force it to `scalingmaxfreq` If you set `scalingmaxfreq` and/or `scalingminfreq` the cpu will never override those values. ### Usage : ### Parameters : Variable name | Default | Type | Comments ----------------|---------|-----------------------------|----------- lowload | 050 | integer between 000 and 999 | 050 = load average : 0.50 midload | 065 | integer between 000 and 999 | 065 = load average : 0.65 highload | 085 | integer between 000 and 999 | 085 = load average : 0.85 scalingminfreq | auto | integer in hertz | 800000 = 800 Mhz scalingmaxfreq | auto | integer in hertz | 2500000 = 2,5 Ghz ### Default commande line : `./scaling.sh &` ### Custom command line example : `lowload=100 highload=200 scalingmaxfreq=2000000 scalingminfreq=1500000 ./scaling.sh &` Enjoy.
  11. PS Gnoboot et la version alpha de Nanoboot
  12. Salut, - il me semble qu'il y a un bootloader compatible ici: http://www.xpenology.nl/boot-images/ - Il n'y a pas de support à proprement parlé, peut être un peu sur xpenology... mais communautaire rien de plus. - Sur le forum et c'est tout il me semble - Oui il ya de l'open source, mais pas vraiment a jour, du coté Xpenology et Gno/Nanoboot : Synology c'est la http://sourceforge.net/projects/dsgpl/ (compiler et sources) Xpenology c'est la https://github.com/andy928/xpenology (repo) et wiki http://xpenology.com/wiki/en/building_xpenology Gno/Nanoboot c'est la https://github.com/sancome/DSM-5.0-4458_dsgpl-4418 (repo) et wiki http://nanoboot.eu.org/source Pour ce qui est des maj, oui avec nanoboot on peut faire les mise à jour, moyennant une ligne de commande. Pour ce qui est des mises à niveau il faut avoir un bootloader à jours pour pouvoir installer le nouveau "firmware". A+