-
Notifications
You must be signed in to change notification settings - Fork 32
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
Possible optimalization in flag_journey_patterns_for_stop #148
Comments
koch-t
added a commit
to koch-t/rrrr
that referenced
this issue
Dec 16, 2014
Instead of high number of non cache-local look-ups for journey_pattern attributes and calendar's, check this once and ban all unsuitable journey_patterns
koch-t
added a commit
to koch-t/rrrr
that referenced
this issue
Dec 16, 2014
Instead of high number of non cache-local look-ups for journey_pattern attributes and calendar's, check this once and ban all unsuitable journey_patterns
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instead of a high number of calls to jp_active_flags and route_attributes we can do a likely more cache-efficient approach by banning in the initial phase of the request, all non-valid journey_patterns and use the banned bitmask to achieve the same.
The text was updated successfully, but these errors were encountered: