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
gulp-sourcemaps
vscode-settings
searchkit
algebra
webpack-watch
dagger-2
swifter
mousemove
device-tree
dynamic-url
android-instant-run
content-type
mock-fs
mvvmcross
apollo-link
git-history-rewrite
polynomial-math
multicasting
didreceiveremotenotification
dom-element
declarative-authorization
soc
hangfire-console
string-utils
viewflipper
azure-managed-disk
borderpane
sanity-testing
rebass
fetchrequest