[Bug] Resource usage spikes upon entering system resources details screen

[vdbhb59]

🐛 Bug Description

So basically when on the main screen the system usage is say 20% for CPU, 10-20% for RAM, but the moment I enter the system resource details screen, the usage spikes like 50% and keeps going higher or remains at a higher level.

📱 Environment

• sysAdmin version: 1.0.28 & previous one as well.
• Android/iOS version: A14
• Device model: Vivo Y35
• Server OS: Debian Bookworm 12.10, Kernel 6.1.0.33

🔄 Steps To Reproduce

1. Open the app and stay on main screen for details to load (3-7 seconds)
2. Navigate to system resource details screen at the bottom
3. See the resources spike like anything

🧐 Expected Behavior

Resources can spike, but not almost to 50-60% from say 20%. Should be minimal to fetch the current details.

🚨 Actual Behavior

Spikes by 50% and more.

📋 Additional Context

There is no logs option anywhere.

📊 Logs

Log output

Paste your logs here

[prathameshkhade]

Thanks for raising the issue!

You are right — the feature is using more resources. I tested it on my Kali Linux setup, and while it didn't cause major spikes for me, I can definitely see that it’s consuming more than expected.

I’ll work on optimizing the code to fetch system details more efficiently and reduce resource usage in the next updates. Thanks again for pointing it out!

[cruizba]

The primary reason seems to be that each fetch of data retrieved from the machine is the result of a command executed directly via SSH:

https://github.com/search?q=repo%3Aprathameshkhade%2FSysAdmin%20sshClient.run&type=code

I think that a potential improvement would involve developing a daemon that the application deploys. This daemon can establish a direct connection between the app and the server, parsing system data and transmitting it through an SSH tunnel using a WebSocket or a similar method, instead of spawning a process for each data fetch. Also instead of using nproc and top or similar tools, maybe parsing directly the data from /proc, /sys could improve the performance.

But SSH command are easier and more portable 🤔 , so trying to analyze which command consumes more or how to reduce the number of spawned processes to fetch data could be another option...

Great app, by the way! It's a fantastic idea :)

[prathameshkhade]

I'm also thinking about using WebSockets, but I need to do some R&D first to explore it properly. I'll also check if there are any other optimal approaches for fetching system data more efficiently.

Thanks a lot for your suggestions

Great app, by the way! It's a fantastic idea :)

I'm really happy to hear that you like the app! It means a lot! 😊