The graph tab is slow with 2000+ beans — what can I do?

[ddsha441981]

Our monolith has thousands of beans and the HTML report graph is heavy in the browser. Any way to limit it?

[ddsha441981]

There's a built-in cap for exactly this:

wiredoctor.max-graph-nodes=2000   # default

Above this many beans, the serialized graph (JSON + HTML view) is capped to top-N by fan-in — with cycle members always kept — so the browser doesn't freeze. 0 = unlimited if you have the RAM and patience.

Two important details:

• Analysis always runs on the full graph. Cycles, smells, critical path, and baseline diff are computed over every bean — the cap only affects what's rendered/serialized, so your CI gates lose nothing.
• To shrink the interesting set instead of just capping, use wiredoctor.scan-packages=com.yourcompany.app,... — framework packages (org.springframework, java., org.apache, …) are already filtered automatically, and wiredoctor.include-framework-smells=false (default) keeps framework beans out of smell rankings so every ranked bean is one you can actually refactor.

All knobs: configuration reference.