Investigate Performance Impact related to Progress tracker

# Research

Due to the way the progress tracker is implemented, we need the to know the total number of items before starting. This often leads to parsing files twice, which might impact performace for large files/projects

## General Idea

We should analyse the performance impact of the progress tracker for projects of different sizes to see if a significant amount of time can be saved.

## Proposed Solution

## Pros/Cons
Pros:
-
-

Cons:
-
-

## Alternatives

Start by locating the progress tracker and the code paths that parse files, then benchmark projects of different sizes with and without the tracker. Done means documenting whether parsing twice causes a significant performance impact and recording the measurements; no files or tests are named in the issue.

Written by the indexing model from the issue text.