dlandon Posted April 18, 2023 Author Share Posted April 18, 2023 2 minutes ago, cjohnson46 said: I previously had it set to 23:00 for "power save" then 09:00 for "Normal (On demand)". So you're saying that the cron won't trigger until it goes past 23:00 or 09:00. It was set last night before 23:00 but didn't trigger/change when I checked at 07:00. I'll give it a couple more tests and see if I can figure it out. I ran a quick test and it did work for me. Quote Link to comment
cjohnson46 Posted April 19, 2023 Share Posted April 19, 2023 You're right, I had it wrong some how in the beginning. It worked this time around. Thank you for helping a dummy like me. Donation on the way. Thanks again Quote Link to comment
s1oz Posted April 23, 2023 Share Posted April 23, 2023 [Enable Intel Turbo/AMD Performance Boost] Can this be done using the command line Quote Link to comment
dlandon Posted April 23, 2023 Author Share Posted April 23, 2023 2 hours ago, s1oz said: [Enable Intel Turbo/AMD Performance Boost] Can this be done using the command line No, Tips and Tweaks doesn't currently support a command line option to control this. Quote Link to comment
zoggy Posted June 15, 2023 Share Posted June 15, 2023 (edited) anyone else seeing that since upgrading to 6.12, the tips and tricks plugin 'Enable syslog Archiving?' option no longer results in the syslog getting archived on restart? i had an issue after upgrading to 6.12 and had to restart to fix, I went to get logs and noticed my last saved logs was the 6.11.5->6.12 reboot. I've not had a chance to restart for a 3rd time to see if it was just an issue during the first reboot of an upgrade or what Edited June 15, 2023 by zoggy Quote Link to comment
dlandon Posted June 16, 2023 Author Share Posted June 16, 2023 1 hour ago, zoggy said: anyone else seeing that since upgrading to 6.12, the tips and tricks plugin 'Enable syslog Archiving?' option no longer results in the syslog getting archived on restart? i had an issue after upgrading to 6.12 and had to restart to fix, I went to get logs and noticed my last saved logs was the 6.11.5->6.12 reboot. I've not had a chance to restart for a 3rd time to see if it was just an issue during the first reboot of an upgrade or what I jsut ran a quick test and it worked for me. Make sure your flash drive doesn't have any errors. Quote Link to comment
zoggy Posted June 20, 2023 Share Posted June 20, 2023 On 6/15/2023 at 8:00 PM, dlandon said: I jsut ran a quick test and it worked for me. Make sure your flash drive doesn't have any errors. tested when upgrading to 6.12.1 and yep worked fine. so no idea what happened on the 6.11.5->6.12.0, gremlins. Quote Link to comment
Masterwishx Posted June 21, 2023 Share Posted June 21, 2023 Having huge amount of User Watches ,after disabled plugin Fiile Activity still have Current User Watches = 12486295 is it normal size ? Quote Link to comment
dlandon Posted June 21, 2023 Author Share Posted June 21, 2023 3 hours ago, Masterwishx said: Having huge amount of User Watches ,after disabled plugin Fiile Activity still have Current User Watches = 12486295 is it normal size ? That shouldn't be a problem. File Activity is not the only process to use Inotify Watches. Quote Link to comment
Masterwishx Posted June 22, 2023 Share Posted June 22, 2023 6 hours ago, dlandon said: That shouldn't be a problem. File Activity is not the only process to use Inotify Watches. Yes i know , but i was thinking after disabled the plugin should be less , but after boot today is even more ! Quote Link to comment
BVD Posted June 22, 2023 Share Posted June 22, 2023 8 hours ago, Masterwishx said: Yes i know , but i was thinking after disabled the plugin should be less , but after boot today is even more ! Pretty normal. Anything you have that 'watches a directory for changes' will add to this list - Plex, Tdarr, Sonarr, NZBGet/SabNZB, Radarr, etc. In the end, it's just a number, albeit one that's useful for keeping the number of disk spinups down. 1 Quote Link to comment
Masterwishx Posted June 22, 2023 Share Posted June 22, 2023 its strange but found : Because each watch is a structure, available memory is also a bottleneck for using inotify. In fact, a watch can take up to 1KB of space. This means a million watches could result in 1GB of extra RAM usage. https://www.baeldung.com/linux/inotify-upper-limit-reached Also when changed to 14506750 i didnt saw memory use increased .... for now i was set back to default ... Quote Link to comment
BVD Posted June 23, 2023 Share Posted June 23, 2023 That's also expected - watching the filesystem isn't free, for sure! Pretty rare it'd take 1KB/watcher though. Quote Link to comment
Masterwishx Posted June 24, 2023 Share Posted June 24, 2023 i moved dockers to br1 becose of macvlan problem: befor i had bond0 of two interfaces and they was both in ethernet nics, now only eth0, should i add also eth1 that is docker network ... Quote Link to comment
Masterwishx Posted June 24, 2023 Share Posted June 24, 2023 Also interesting why custom network br0 or br1 in docker does not have internet access from local net ? Quote Link to comment
dlandon Posted June 24, 2023 Author Share Posted June 24, 2023 7 hours ago, Masterwishx said: i moved dockers to br1 becose of macvlan problem: befor i had bond0 of two interfaces and they was both in ethernet nics, now only eth0, should i add also eth1 that is docker network ... Yes, if you want to make adjustments to that NIC also. 1 Quote Link to comment
dlandon Posted June 24, 2023 Author Share Posted June 24, 2023 2 hours ago, Masterwishx said: Also interesting why custom network br0 or br1 in docker does not have internet access from local net ? Changes have been made in 6.12. Refer to the release notes. 1 Quote Link to comment
Gershy13 Posted June 29, 2023 Share Posted June 29, 2023 What should I set the governor to for a Ryzen 3700x? I'm not worried about power or temperature, I just want the best performance. Load type varies; Plex, MC servers, Home assistant, other dockers, etc. Quote Link to comment
dopeytree Posted July 15, 2023 Share Posted July 15, 2023 (edited) Seems to be an issue with changing scaling governor. It seems to get stuck on one or the other. Right now it's 2.24am so it should have swapped to power save. Anyone else having this issue/s on 6.12.x moulin-rouge-diagnostics-20230714-2059.zip Edited July 15, 2023 by dopeytree Quote Link to comment
dlandon Posted July 15, 2023 Author Share Posted July 15, 2023 What Governor shows on the right side. Can you switch the 'Normal' mode and see it change on the right hand side? Quote Link to comment
enlinks Posted July 23, 2023 Share Posted July 23, 2023 (edited) I think the Tips and Tweaks output for Current User Watches is wrong, if I had "-1449511" watches I should be seeing other issues. I ran this manually along with a script below and they are both giving the same results: find /proc/*/fd \ -lname anon_inode:inotify \ -printf '%hinfo/%f\n' 2>/dev/null \ \ | xargs grep -c '^inotify' \ | sort -n -t: -k2 -r /proc/24962/fdinfo/21:19423 /proc/24968/fdinfo/21:10640 /proc/34743/fdinfo/66:4801 /proc/9574/fdinfo/22:1254 /proc/20814/fdinfo/221:521 /proc/1324/fdinfo/5:41 etc..... Github Script: curl -s https://raw.githubusercontent.com/fatso83/dotfiles/master/utils/scripts/inotify-consumers | bash INOTIFY INSTANCES WATCHES PER COUNT PROCESS PID USER COMMAND ------------------------------------------------------------ 19423 1 24962 nobody /app/Tdarr_Server/Tdarr_Server /snapshot/be/srcug/fo 10640 1 24968 nobody /app/Tdarr_Server/Tdarr_Server /snapshot/be/srcug/fo 4801 1 34743 nobody /usr/lib/plexmediaserver/Plex Media Server etc....... 36806 WATCHES TOTAL COUNT It seems that the Tips and Tweaks script (took this command from the script) is only adding the PIDs together and not the actual count of active inotify watches? I grepped for my Plex PID and got a match. find /proc/*/fd -lname anon_inode:inotify | cut -d/ -f3 | awk '{s+=$1} END {print s}' 2138818 find /proc/*/fd -lname anon_inode:inotify | cut -d/ -f3 | grep 34743 34743 If we dig into the PID though we get the actual inotify watch count, example count from my Plex PID: grep -c '^inotify' /proc/34743/fdinfo/66 4801 Edited July 23, 2023 by enlinks grammer Quote Link to comment
dlandon Posted July 23, 2023 Author Share Posted July 23, 2023 6 hours ago, enlinks said: I think the Tips and Tweaks output for Current User Watches is wrong, if I had "-1449511" watches I should be seeing other issues. Yes, there is an issue with the calculation. I'll issue an update today. 1 Quote Link to comment
enlinks Posted July 23, 2023 Share Posted July 23, 2023 1 hour ago, dlandon said: Yes, there is an issue with the calculation. I'll issue an update today. No rush! At least with this post people can manually check it for the time being. Appreciate everything you all do! Quote Link to comment
Daniel15 Posted September 7, 2023 Share Posted September 7, 2023 (edited) Setting the CPU scaling governor to "power save" but keeping turbo boost enabled still seems to cap the CPU at the non-turbo speeds. Is that expected? I had to manually set the `scaling_freq_max` to the maximum frequency (cpuinfo_max_freq) per core: for x in /sys/devices/system/cpu/cpu*/cpufreq/; do cat $x/cpuinfo_max_freq > $x/scaling_max_freq; done It'd also be useful to have an option to control the energy/performance preference for the hardware-managed P-states (HWP) of Intel CPUs: The `energy_performance_preference` setting (`/sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference`) defaults to `balance_performance` but it can be set to `balance_power` to tell the CPU to focus on energy saving instead of performance. (the CPU scaling governor affects the software governor in Linux, while `energy_performance_preference` affects the CPU's internal logic) with energy_performance_preference set to balance_power, the CPU cores won't turbo unless they really needs to (if CPU usage is high enough to need it). Edited September 7, 2023 by Daniel15 Quote Link to comment
dlandon Posted September 7, 2023 Author Share Posted September 7, 2023 2 hours ago, Daniel15 said: Setting the CPU scaling governor to "power save" but keeping turbo boost enabled still seems to cap the CPU at the non-turbo speeds. Is that expected? Probably. Although I'm not a cpu governor expert. 2 hours ago, Daniel15 said: It'd also be useful to have an option to control the energy/performance preference for the hardware-managed P-states (HWP) of Intel CPUs: The `energy_performance_preference` setting (`/sys/devices/system/cpu/cpu*/cpufreq/energy_performance_preference`) defaults to `balance_performance` but it can be set to `balance_power` to tell the CPU to focus on energy saving instead of performance. (the CPU scaling governor affects the software governor in Linux, while `energy_performance_preference` affects the CPU's internal logic) It looks like this applies to the intel_pstate governor only. There are more than two states available on my inel cpu: root@MediaServer:~# cat /sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences default performance balance_performance balance_power power root@MediaServer:~# I don't understand the 'default' setting - maybe a default cpu setting. On my system the default is: root@MediaServer:~# cat /sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference performance root@MediaServer:~# Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.