What is it doing on my large repo?

[dimaqq]

Low, but non-zero CPU usage, no massive memory usage...

[dimaqq]

Full run resuts:

🦐/c/vipyrdocs (master) [SIGINT]> time cargo run  ../operator > /dev/null
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.20s
     Running `target/debug/vipyrdocs ../operator`

________________________________________________________
Executed in  281.20 secs    fish           external
   usr time  273.63 secs    0.44 millis  273.63 secs
   sys time    2.01 secs    2.02 millis    2.01 secs

Repo: https://github.com/canonical/operator

(ofc., it does complain about tons of things in the end)

[alithethird]

This is super interesting!

I ran the following tests in a multipass machine with 8 cores and 16gigs of ram.

I tried to run the release version and it is much faster:

➜  vipyrdocs git:(master) time cargo run --release ../operator > /dev/null
    Finished `release` profile [optimized] target(s) in 0.08s
     Running `target/release/vipyrdocs ../operator`
cargo run --release ../operator > /dev/null  2.16s user 0.06s system 97% cpu 2.274 total

but the unoptimized version is also much faster then yours:

➜  vipyrdocs git:(master) time cargo run  ../operator > /dev/null
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.04s
     Running `target/debug/vipyrdocs ../operator`
cargo run ../operator > /dev/null  10.20s user 0.24s system 99% cpu 10.516 total

I do cross file checks to discover inheritances and run checks on abstract/implementation docstrings. I would say it is the most heavy computation the code does but I don't think this is the issue here.