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
qpainter
tomcat
generic-variance
tribe-event-tickets
unstated
on-delete
snowpipe
file-diffs
lifetimes-python
dynamic-language-runtime
sequentialfeatureselector
konsole
gringo
simplex-noise
fiddle
pallet
safearray
graphql-spring-boot
memcachedb
dictionary
package-design
okta-api
rxjs5
svc
glitch-framework
pfx
django-dynamic-scraper
create.js
public-key
swd