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
pymodbustcp
datafeed
owin-security
name-length
tembeddedwb
custompaging
angular-observable
concurrent-collections
jxbrowser
net.tcp
spring-kafka-test
minifilter
nodatime
touchimageview
function
passenger-nginx
acoustic-telemetry
physics-engine
qt5.4
jquery-wrap
postman-collection-runner
components
nitrogen
appx
formatted
android-authenticator
common-lisp
local-storage
facebook-custom-audience
spring-data-jdbc