Open yarikoptic opened 3 weeks ago
This bugfix helps https://github.com/con/duct/commit/b6c9219bc3a20f781f321f906396ba0a25bc5250
Here's some fun dogfooding :)
$ duct duct sleep 100
duct is executing duct sleep 100...
Log files will be written to .duct/logs/2024.06.21T13.06.49-1223368_
duct is executing sleep 100...
Log files will be written to .duct/logs/2024.06.21T13.06.49-1223371_
Exit Code: 0
Command: sleep 100
Log files location: .duct/logs/2024.06.21T13.06.49-1223371_
Wall Clock Time: 100.003 sec sec
Memory Peak Usage (RSS): 1920 KiB
Memory Average Usage (RSS): 1920.000 KiB
Virtual Memory Peak Usage (VSZ): 221584 KiB
Virtual Memory Average Usage (VSZ): 221584.000 KiB
Memory Peak Percentage: 0.0%
Memory Average Percentage: 0.000%
CPU Peak Usage: 0.0%
Average CPU Usage: 0.000%
Samples Collected: 98
Reports Written: 2
Exit Code: 0
Command: duct sleep 100
Log files location: .duct/logs/2024.06.21T13.06.49-1223368_
Wall Clock Time: 100.073 sec sec
Memory Peak Usage (RSS): 17920 KiB
Memory Average Usage (RSS): 17196.735 KiB
Virtual Memory Peak Usage (VSZ): 682564 KiB
Virtual Memory Average Usage (VSZ): 627538.367 KiB
Memory Peak Percentage: 0.0%
Memory Average Percentage: 0.000%
CPU Peak Usage: 4.0%
Average CPU Usage: 1.658%
Samples Collected: 98
Reports Written: 2
Average CPU Usage: 1.658%
is an improvement, but still using a lot more power than we probably need.
ATM running a singularity container through duct shows 2-3% CPU of duct. I wonder what it is doing. Would be worth checking with py-spy etc some of its runs to see what it spends time on -- even though just a little, given how little it needs to do I would expect it to be even lower
but I could be wrong.