1 hour ago, BVD said:

I've found myself repeatedly sending folks the command below to run on their servers while trying to help them track down things like random disk spinup, and wondered if we might add the it to the help section for the "Max Watches fs.inotify.max_user_watches" section? It's a simple one liner that gives the total current watchers in use:

find /proc/*/fd -lname anon_inode:inotify | cut -d/ -f3 | awk '{s+=$1} END {print s}'

 

I suppose it could instead have something within the plugin that just runs the above and displays it as 'currently used watchers' or something as well, but that'd take a bit more doing, so I figured I'd go for the low hanging fruit here 😅

Or if you've got a better way to get to the info (or perhaps a more reliably accurate one - the number changing constantly can make it hard for folks to nail down as new pids spawn/die), I'm all for it of course! Just figured an easy way for folks to check this being on hand in the tool would be cool.

 

Thanks for all your work to better the UI experience @dlandon!!

Thanks for the suggestion.  Nice idea.  I'm including this in the UI.  I'm not a fan of users having to go to the command line to do things.

Well, if you wanna double down on it, you could just integrate this:

https://github.com/mikesart/inotify-info

 

Builds perfectly on unraid inside of 5 seconds lol

 

Thanks so much for the work you continue to put into these quality-of-life-like additions - it's hugely appreciated, and truly fills out the ecosystem ❤️ 

My server uses a i9 11-900t but an ES (test) version so as such unraid doesn't display it's an i9 but if you request the cpu info it does know its a model 167 & that it ranges from 0.8ghz - 4.5ghz

 

Do you think it's worth me telling unraid what the CPU is?

 

I have no problem boosting but it doesn't scale down properly. Any small task will boost up to full speed.

Looking for some kind of middle ground where it can boost say from 0.8 - 2ghz. 

 

Then another setting would do 2 - 4.5ghz when running a cron script.

 

Currently performance does full wack 3.8 - 4.5ghz

and powersave does 0.8 - 1.1ghz

 

Thanks

I was just playing with this app and found that the link to the WIKI for it does not work.  In fact, none of the links in the app work.  I believe they still point to lime-technology.com...

1 hour ago, Frank1940 said:

I was just playing with this app and found that the link to the WIKI for it does not work.  In fact, none of the links in the app work.  I believe they still point to lime-technology.com...

The links haven't been updated in the plugin for a long time.  They will be addressed in the next release.

I have a pair of Broadcom 10gig ethernet ports on my motherboard.  I am unable to change the setting for Rx/Tx Buffer.  Is this not supported for this driver?

 

i have found this info for the driver unRaid is loading for them:

 

https://docs.oracle.com/cd/E87266_01/html/E87989/cehbiiej.html#scrolltoc

 

 

 

TIA

 

Edited February 16, 20233 yr by bpl294
changed pic

25 minutes ago, bpl294 said:

Is this not supported for this driver?

Doesn't look like it.

11 minutes ago, dlandon said:

Doesn't look like it.

could it be? or any plans to add it?

5 minutes ago, bpl294 said:

could it be? or any plans to add it?

Doesn't look like it is settable in the driver from the link you showed me.

Getting lots of wrong notices. It keeps saying its starting a partity check when parity is valid (it did a check a few days ago).

Also showing notifications from quite a while ago.

Should I delete the appdata folder & reinstall to force clear logs?

6 hours ago, dopeytree said:

Getting lots of wrong notices. It keeps saying its starting a partity check when parity is valid (it did a check a few days ago).

Also showing notifications from quite a while ago.

Should I delete the appdata folder & reinstall to force clear logs?

This has nothing to do with the Tips and Tweaks plugin.

11 hours ago, dopeytree said:

It keeps saying its starting a partity check when parity is valid (it did a check a few days ago).

Parity checks are never automatically started by the system without a good reason or something configured to start them.    You should try opening a new thread and posting your system's diagnostics zip file taken when this happens so we can try and work out what is going on.

There is no parity check happening.

The plugin is not clearing old pop up notifications.

Manually removed them in the plugin now and all good.

I found "Power Save" is the only option in "Power Saving CPU Scaling Governor", can you help for checking ?

unraid-diagnostics-20230321-2031.zip

On 2/25/2023 at 11:24 AM, dopeytree said:

The plugin is not clearing old pop up notifications.

Do not quite understand what you mean by this.    There is no concept within the plugin of ‘old’ notifications that need clearing as they are simply generated in real time as appropriate and then no record kept within the plugin of this happening.    Are you talking about clearing notifications at the Unraid level?

21 minutes ago, Lilarcor said:

I found "Power Save" is the only option in "Power Saving CPU Scaling Governor", can you help for checking ?

unraid-diagnostics-20230321-2031.zip 171.5 kB · 0 downloads

What CPU driver is shown on the right side if the Tips and Tweaks page?

1 minute ago, dlandon said:

What CPU driver is shown on the right side if the Tips and Tweaks page?

It's "Driver: Intel Pstate", I am using E3 1240V5 with MB SuperMicro X11SSH-F

Edited March 21, 20233 yr by Lilarcor

3 minutes ago, Lilarcor said:

It's "Driver: Intel Pstate", I am using E3 1240V5 with MB SuperMicro X11SSH-F

The only Scaling Governors that driver offers are "Performance" and "Power Save".

2 minutes ago, dlandon said:

The only Scaling Governors that driver offers are "Performance" and "Power Save".

Thanks. Does it mean my CPU is running under power save or Performance mode if my current "Normal CPU Scaling Governor" is set to "Performance" ?

34 minutes ago, Lilarcor said:

Thanks. Does it mean my CPU is running under power save or Performance mode if my current "Normal CPU Scaling Governor" is set to "Performance" ?

"Performance" means performance mode.

Hi there and thanks for the great plugin and support. I'm not experiencing any issues with it or my system. BUT, should I be concerned about these numbers? 😋

 

7 hours ago, Sqibble said:

Hi there and thanks for the great plugin and support. I'm not experiencing any issues with it or my system. BUT, should I be concerned about these numbers? 😋

 

You don't have enough user watches.  Increase the 'Max User Watches' to at least 2,700,000.

This plugin is the best!  It has saved me so much money.  I'm not sure this is the place to post issues, but I have just have one problem.  It seems the "Schedule CPU Power Saving Mode" isn't working for me.  I made sure my Unraid date and time are correct, set the schedule properly, but it still won't change to "Power saving" mode during the schedule.  I'm on Unraid 6.11.5 with Tips & Tweaks plugin dated "2023.02.01".  I att ached my diag file.  Thanks!

 

skynet-diagnostics-20230418-0915.zip

13 minutes ago, cjohnson46 said:

This plugin is the best!  It has saved me so much money.  I'm not sure this is the place to post issues, but I have just have one problem.  It seems the "Schedule CPU Power Saving Mode" isn't working for me.  I made sure my Unraid date and time are correct, set the schedule properly, but it still won't change to "Power saving" mode during the schedule.  I'm on Unraid 6.11.5 with Tips & Tweaks plugin dated "2023.02.01".  I att ached my diag file.  Thanks!

 

skynet-diagnostics-20230418-0915.zip 262.08 kB · 0 downloads

Please realize that if you make a change to the settings, the CPU mode be set to "On Demaind" and will not change to "Power Save" until 23:00 hours.  UD sets up crons to switch the mode, but doesn't switch the mode if it is in the timeframe when changes are made.

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.