-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Searching for transfer rules is slow #2078
Comments
Does this optimization significantly improve runtime? If so, then we have to rethink using Java 8 features. |
Yes, at least when the lists are empty, not constructing the empty streams saves several seconds per request. Matthew Wigginton Conway ---- On Mon, 03 Aug 2015 19:01:06 -0400 Andrew Byrd <notifications@github.com> wrote ---- Does this optimization significantly improve runtime? If so, then we have to rethink using Java 8 features. |
I should add that this function is called millions of times per request and usually does nothing. This is a particular use case (constructing lots of empty streams) that probably isn't common. |
… declarative loops. fixes opentripplanner#2078.
Searching for transfer rules in RaptorWorkerTimetable::getFrequencyDeparture is close to 70% of runtime on pure-frequency networks. Looks like this is largely due to stream creation.
The text was updated successfully, but these errors were encountered: