[pgrouting-users] pgrouting speed

[Daniel Kastl]

Hi Emre,

How large is your network?
I think you could do it faster, but it depends also on your hardware and you
might also be able to make some changes in the postgresql configuration.
Ride the city for example is using pgRouting and the size of the cities
should be comparable to Istanbul:
http://www.ridethecity.com/

<http://www.ridethecity.com/>To improve speed you can check:

   - Indices for attributes used in your query
   - ID numbering (very high ID's make it slow)
   - complicated cost calculation and joins between tables. If you have
   this, maybe you could pre-calculate some costs.

In general as less network data you load with your select as faster it is.

Daniel


2011/2/2 Emre Koc <emrekoch at gmail.com>

> Hi All,
>
> What is the average speed for running a shortest path query over a large
> city ? For Istanbul it takes about 3.5 seconds to find a path in my setup. I
> slightly modified sp_smart_directed function and using it right now but I am
> not sure if the speed is ok. If I reduce delta value for this function
> (which is limiting the region to be processed) operation is speeding up but
> it cannot find paths that exceeds the region.
>
> If my query time is slow what is your suggestion on speeding things up? I
> added index for the_geom column. Is there anything to be done extra?
>
> Thanks,
>
> /emre
>
> _______________________________________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
>


-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20110202/b69ce436/attachment.html