rrrr
rrrr copied to clipboard
Possible optimalization in flag_journey_patterns_for_stop
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.