Skip to content

Bicycle access is slow #6781

@t2gran

Description

@t2gran

Expected behavior

A short trip search should return within resonable time.

Observed behavior

Image

Search

Some searches take a very long time (>10s), while most searches take an acceptable time (<2s). This could be related to bicycle access. I run the same query, only changing the access mode and this is the response times:

Mode response times
bicycle 14.22s, 13.26s, 17.77s
foot 0.615s, 0.588s
car_park 0.706s
car 2.4s

All searches return at least one result, except the using car as access mode.

This performance problem goes away if we exclude BIKE transfers in the build-config.json. The test is repeatable, I can change the origin and destination coordinates - I still get the same behaviour.

Note! I am not sure the the bike access is the direct cause of the problem. If I repeat the exact same search, I sometimes get fast response. This might be a cache or Java GC problem triggered by the bicycle access.

Version of OTP used (exact commit hash or JAR name)

v2.8.0-SNAPSHOT (May-2025) 0962f46

Data sets in use (links to GTFS and OSM PBF files)

Entur Norway

Command line used to start OTP

Router config and graph build config JSON

build-config.json
{
  "configVersion": "v2.8.0-entur-105",
  "dataImportReport": true,
  "subwayAccessTime": 0,
  "embedRouterConfig": true,
  "areaVisibility": true,
  "platformEntriesLinking": true,
  "staticParkAndRide": true,
  "staticBikeParkAndRide": true,
  "maxDataImportIssuesPerFile": 1000,
  "maxTransferDuration": "30m",
  "distanceBetweenElevationSamples": 25,
  "multiThreadElevationCalculations": true,
  "boardingLocationTags": [],

"transferParametersForMode": {
"CAR": {
"disableDefaultTransfers": true,
"carsAllowedStopMaxTransferDuration": "3h"
}
},
"transferRequests": [
{
"modes": "WALK"
},
{
"modes": "WALK",
"wheelchairAccessibility": {
"enabled": true
}
},
{
"modes": "BICYCLE"
},
{
"modes": "CAR"
}
],
"osmDefaults": {
"osmTagMapping": "norway",
"timeZone": "Europe/Oslo"
},
"osmCacheDataInMem": "true",
"transitServiceStart": "-P2D",
"transitServiceEnd": "P5D",
"netexDefaults": {
"feedId": "RB",
"sharedFilePattern": "stops.*\.xml",
"sharedGroupFilePattern": "
(\w{3})(_flexible)?shared_data.xml",
"groupFilePattern": "(\w{3})
.*\.xml",
"ignoreFareFrame": false
},
"streetGraph": "streetGraph-${otp.serialization.version.id}.obj",
"graph": "graph-bicycle-${otp.serialization.version.id}.obj",
"buildReportDir": "report"
}

Steps to reproduce the problem

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions