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
system.commandline
mindmap
qemu-device
pancakeswap
twitter-bootstrap-2
angular-ngrx-data
freeimage
material-icons
merge-file
plc4x
openedx
next
tinymce-4
node-config
visual-studio-2008
copy-elision
python-all-function
virus
servicepointmanager
sqslistener
negation-as-failure
blender-2.67
radscheduler
blink-developer-tools
state-diagram
idempiere
qquickwidget
cs231n
2d-context-api
ecmascript-next