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
404-page
slickr
miniconda
naturalid
intersystems
ptv-vissim
beta-testing
case-sensitive
undelete
edsdk
runtime-type
s3-rewrite-rules
groovy-console
ray
cargo
android-doze
grpc-kotlin
vichuploaderbundle
media-buttons
yellow-pages
distro
docking
build-automation
pyusb
sharepoint-userprofile
pyhdf
auto-sklearn
outlook-object-model
rnetlogo
telerik-open-access