Improve the analyze performance

[zhoufenqin]

I use windup and kantra to analyze the same repo,

• Repo: https://github.com/spring-projects/spring-petclinic.git

• Command：
  windup: windup --input ./spring-petclinic --target cloud-readiness linux discovery --overwrite
  kantra: kantra analyze --input ./spring-petclinic --output ./analyze.report --target cloud-readiness --target linux --overwrite

I use /usr/bin/time -v {command} 2>&1 | tee benchmark.log to collect the timecost/cpu/memory, there are big gap about it:
windup:

kantra:

kantra is very slow and cost more resources.

Question:

1. how to improve the kantra performance, i think it should be improved in lsp because it provide the main logic
2. how to deep into the root cause so i can also do more analysis in my side

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[shawn-hurley]

I would be curious if you could find the location by using the [https://github.com/konveyor/analyzer-lsp/blob/b062f3757592bdb4da8f5b20e48ee7319faaca93/README.md?plain=1#L49] to see what is taking the time.

From my experience, the significant slowdown isn't in the language server, but in grep; file searching seems to be the high cost.

If you are finding something else I would very much like to see it, and talk about what our next steps should be