Hi @Bud, This could improve your case since the performance improvement will allow information about the remote EGDB workspace that is storing the route event layer data source to be cached.
Particularly, repetitive processes will benefit; the first time you run a tool it will not be faster than any previous release, but any subsequent runs of tools against data sources in the same workspace will have better performance. This is because it will use locally cached sets of properties rather than traveling across the network for each request.
