To identify the step that is using most of the computation time, I ran cProfile and got the following result: ncalls tottime percall cumtime percall fil
clpfd
jscript
dart-mockito
chopper
dse
magenta
tvirtualstringtree
slt
quake2
composite-component
yahoo
hadoop
qgraphicsscene
pytest-qt
android-bottomappbar
ngrx-entity
webmail
wsc
python-2to3
gaussian-mixture-model
azure-anomaly-detector
netbeans-12
canon-sdk
docker-quickstart-terminal
composite-key
gosec
facial-landmark-alignment
smartphone
google-aiy
pinvoke