Increased plugin latency by 1.3.1

greetings,
since the force wipe update, simple status allocates increasingly more server resources, especially cpu time.
a reload last night calmed whatever is going on for almost 24h until it started again.
config values are default and permission status latest version is being utilized 

{

  "ChatMessageSteamId": 0,

  "ToggleStatusCommand": "ts",

  "UseCustomVitals": true,

  "UseInternalCustomVitalsWrapper": true,

  "ForceCustomVitalsForUnsupportedStatuses": false,

  "IgnoreAdvancedStatus": false

}

Hey, thanks for the report and the graphs. The increase in the 1-second average is worth investigating.

Could you confirm your exact SimpleStatus version, whether you’re using Oxide or Carbon, and whether AdvancedStatus is installed? Please also send your Permission Status config and any SimpleStatus backend/fallback messages from the console

Roughly how many players were online before and after the increase around 00:30? Also, after reloading SimpleStatus, does the 1 second average drop as well, or only the cumulative total?

I’ve identified some potentially unnecessary work in SimpleStatus’s update paths, but I need those details to narrow down what’s happening on your server

quickest support on this platform bless your soul
sure thing

confirmed 1.3.1
oxide
advanced status = not installed
12 player online 00:30 decreasing player count eu server
permission status cfg attached
[SimpleStatus] UseCustomVitals is enabled, but the CustomVitals backend is unavailable (Facepunch CustomVitals API is unavailable). Falling back to Legacy CUI.

prior reload - after

permstatus cfg.json

Thanks, that pretty much confirms what I suspected

You re on 1.3.1, using Oxide, without AdvancedStatus, and the startup log shows that CustomVitals was unavailable and SimpleStatus fell back to Legacy CUI

I just uploaded version 1.3.2. It fixes a startup timing bug where SimpleStatus could initialize before the Facepunch server state was fully ready, causing CustomVitals to be marked unavailable until the plugin was manually reloaded

Please update to 1.3.2 and do a full server restart, not just a plugin reload. After startup, you should see a message saying that the CustomVitals backend is available through the SimpleStatus internal wrapper

If it starts correctly on CustomVitals, the whole rendering path should be considerably lighter, since it won't need the same frequent CUI layout checks and redraw work

I m also going to go through the Legacy CUI path myself and see if there's an actual performance issue there that needs fixing, because I don't want to just assume the fallback is behaving optimally

Based on your logs and the before/after reload graphs, I think the performance issue is very likely tied to the Legacy CUI path rather than CustomVitals itself

If the CPU usage still starts climbing again on 1.3.2 while CustomVitals is confirmed active, send me a new graph and the SimpleStatus startup messages and I'll keep tracing it

Also, did you see some messages in console like "Status 'xxx' from plugin 'SomePlugin' requires the Legacy CUI integration because it uses a progress bar..."?

appreciate the elaboration. if i shall observe this behavior with your updated version i'll chime in and let you know
searching Legacy CUI integration does not find a result in console log