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
plsql-package
rancher-rke
azure-webjobssdk
sas-metadata
sharepoint-2010
test-bench
libreoffice
scroll-snap-points
authorized-keys
camediatiming
timemachine
css-rem
re2
uninitialized-constant
distcp
gnu-toolchain
countable
libavformat
express.io
electron-window
office-fabric
bearing
amazon-inspector
word-interop
denormalized
iqr
chamilo-lms
winget
formal-verification
bullet-chart