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
pyxel
coordinator
python-iptables
recordset
unique
const-method
ui-thread
nsvisualeffectview
android-app-links
axios-retry
mupdf
gotjs
flac
mono.cecil
angular2-services
na.approx
google-chrome-android
precompile
multi-user
log-likelihood
intel-mkl
printer-control-language
gcc12
sum-type
travel-time
tabulate
esmodules
stripes
static-pages
pose-estimation