Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It only takes a minute to sign up.
Sign up to join this community
I have a large osm dataset. When I execute a pgr_ksp query, it takes +30 minutes
Example:
SELECT seq , id1 , id2 , cost
FROM pgr_ksp(
'SELECT id, source, target, cost FROM myways',
524356, 1210854, 2, false);
My virtual server has 4 processors and 3GB RAM. My ways table has 2290470 rows.
The other functions work normally but pgr_ksp does not.
Does anyone know what is the problem?
If you have a large network, then selecting the whole network in your query will always become slow whatever routing algorithm you use.
Have you tried to only select the network you actually need and not the whole 2 Mio. rows? The easiest way is to limit the selected area using a BBOX, see for example Why is any pgr_* routing function taking forever based on OSM data in an pgrouting enabled DB
Because KSP is more complex than Dijstra fro example it's likely to be slower, and if you try it with a large network such as yours the difference may become more obvious.
