mirror of
https://github.com/mvt-project/mvt.git
synced 2026-10-18 21:47:15 +02:00
Donncha Ó Cearbhaill
06cea62a40
Command.run() times every module and measures how much the process's peak resident set size grew while it ran. Both are logged at INFO in one line per module and written to info.json under module_stats, in run order, so any run says which module cost what and CI can compare a branch against main. ru_maxrss is the process peak, so a module's growth is how much it raised the high-water mark, which is what matters on a host without swap; a module running after a bigger one reports 0. Where the resource module is unavailable the growth is reported as 0.