Submission checklist
Plugin
avivbintangaringga/nix-monitor
Plugin version
1.2.0
Bug description
By default, the plugin launches a du command to get the nix store size every 10 minutes, and it's canceled every 5 minutes if it takes too long.
I'm not sure why such values have been chosen, considering that despite being on an NVMe drive, 5 minutes wasn't enough (in this case, with a nix store size of around 95GB), so the command would be canceled and relaunched every 5/10 minutes respectively, eating away at my CPU and I/O for no reason.
On top of that, I'm unsure of the need of having to scan the store every 10 minutes, I don't think the user cares that much about the store size.
Steps to reproduce
Your mileage may depend on your exact hardware and nix store size, but since the command runs by default, just check btop or something and you'll notice a du command running for long periods.
Expected behavior
The default values should be increased to more sensible defaults. Personally, I don't even care about this feature, so even better would be to add a toggle to completely disable this scan.
Actual behavior
By default it happens way too often and may even cancel/relaunch the command intermittently, constantly eating at I/O and CPU.
Logs / error output
Noctalia version
v5.0.0
Compositor
Niri
Environment information
Additional context
No response
Submission checklist
Plugin
avivbintangaringga/nix-monitor
Plugin version
1.2.0
Bug description
By default, the plugin launches a du command to get the nix store size every 10 minutes, and it's canceled every 5 minutes if it takes too long.
I'm not sure why such values have been chosen, considering that despite being on an NVMe drive, 5 minutes wasn't enough (in this case, with a nix store size of around 95GB), so the command would be canceled and relaunched every 5/10 minutes respectively, eating away at my CPU and I/O for no reason.
On top of that, I'm unsure of the need of having to scan the store every 10 minutes, I don't think the user cares that much about the store size.
Steps to reproduce
Your mileage may depend on your exact hardware and nix store size, but since the command runs by default, just check btop or something and you'll notice a du command running for long periods.
Expected behavior
The default values should be increased to more sensible defaults. Personally, I don't even care about this feature, so even better would be to add a toggle to completely disable this scan.
Actual behavior
By default it happens way too often and may even cancel/relaunch the command intermittently, constantly eating at I/O and CPU.
Logs / error output
Noctalia version
v5.0.0
Compositor
Niri
Environment information
Additional context
No response