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
liquibase-cli
caroufredsel
hcatalog
mandelbrot
range-header
nstableheaderview
acceleo
stack-overflow-jobs
controls
lapack
terminusdb
siemens
operationqueue
localhost
django-piston
windows-creators
jmeter-5.0
docker.dotnet
altitude
scriptella
exif
django-mssql-backend
terminal
jclouds
fixed-width
gd
mediacapture
django-1.7
polymerfire
flags