C++ view AST / printAST.ql performance analysis

Is there anything the end user can do to triage extremely slow 24hr+ printAST requests? It's for a single file that has an include that relies on a lot of other compilation units. The 'db-cpp' folder is 92GB - creating a smaller slice with only this file and required compilation units wouldn't make it any faster, I think, as this query should only be accessing data related to this file to begin with? If that's a valid approach to improve this query's perf - is there an easy way to slice the existing DB or does a new build need to be run with some arg?

"Iteration 30-32" took ~4hrs each doing something similar to `DumpDeclaration::getTemplateArgumentsString`. Java has an 8gb heap and pegs a single core. Is there some preferred tracing for codeql's java components I can capture?

Reason I'm trying to view AST is just so that I don't have to guess at how the code flow I'm looking at is represented by codeql 😄