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
pystan
gs-vlookup
azure-elastic-sharding
ckeditor4.x
bullet
oculus-runtime
set-analysis
statements
orgchart
format-list
ec2-ami
8085
azure-media-services
executionpolicy
asyncsocket
ssh
jdk1.8.0
ios-universal-links
revenue
codio
huge-pages
aws-iot
stdmap
ott
jakarta-mvc
24-bit
nautowired
rocketmq
passenger-apache
anti-patterns