Performance

[edwinkortman]

Due to performance issues, tests in CI are failing because they are hitting the time-out.
e.g. #310

We also noticed that when running the analysis on a small repository, it'll take longer than we want to (+1 minute easily).

This issue exists to collect data on our current performance state.

[edwinkortman]

Analyzing fixture repository

Command: freshli analyze https://github.com/corgibytes/freshli-fixture-java-test
Total time running: 1m 56s

• Corgibytes.Freshli.Cli.Functionality.Environment.GetListOfFiles throws 168 exceptions
• Corgibytes.Freshli.Cli.Functionality.Environment.GetListOfFiles allocates 119 MB

• 27.3% of the total time is spent on Corgibytes.Freshli.Cli.Functionality.Invoke.Command

[edwinkortman]

Adding caching

Caching was added in this PR: #325
If the PR is merged & approved, the Package results are saved to the database saving us from calling the agent multiple times for the same package.

Command: freshli analyze https://github.com/corgibytes/freshli-fixture-java-test
Total time running: 1m 21s (before 1m 56s)

[edwinkortman]

With these PRs added, I think it's best to revisit this issue once we got those implemented. The main culprits I could identify were calls to the agent.

corgibytes/freshli-agent-java#34
corgibytes/dependency-history-maven#24