looking at your configuration, you are only using the basic Dijkstra routing, which takes much longer as routes get longer.
If you update the cycling profiles to be like the following, it will then use the algorithms that are designed to be much faster for longer distances, but at the expense of not taking into account turn restrictions.
"profile-bike-regular": {
"profiles": "cycling-regular",
"parameters": {
"encoder_options": "consider_elevation=true|turn_costs=true|block_fords=false",
"elevation": true,
"preparation": {
"min_network_size": 200,
"min_one_way_network_size": 200,
"methods": {
"ch": {
"enabled": true,
"threads": 8,
"weightings": "recommended"
},
"lm": {
"enabled": true,
"threads": 8,
"weightings": "recommended",
"landmarks": 8
},
"core": {
"enabled": true,
"threads": 8,
"weightings": "recommended,shortest",
"landmarks": 32
}
}
},
"execution": {
"methods": {
"astar": {
"approximation": "BeelineSimplification",
"epsilon": 1
},
"ch": {
"disabling_allowed": true
},
"lm": {
"disabling_allowed": true,
"active_landmarks": 6
},
"core": {
"disabling_allowed": true,
"active_landmarks": 6
}
}
},
"ext_storages": {
"WayCategory": {},
"WaySurfaceType": {},
"HillIndex": {},
"TrailDifficulty": {}
}
}
}
Please be aware though, doing these will increase the amount of RAM needed and the amount of time needed for building graphs.