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
external-dns
sysinfo
7-bit
convert-tz
controltemplate
loop-device
calculation
shortest-path
quarkus-oidc
chrome-canary
basex
froogaloop
fzf
help-system
catalog
non-linear
data-extraction
libexif
aws4c
kendo-mvvm
automation-null
jank
ggiraphextra
transactional-email
autonumber
maven-module
android-switch
bacnet
onnewintent
web-developer-toolbar