<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I have seen this mentioned several times, but never got an idea of what a very high ID is? What's very high?<div><br></div><div>I have not tried this, but have considered using a smaller region initially and if a route is not found, jump to a bigger region and re-query, then perhaps fall back to an even bigger region before failing. If 90% of your routing will fit into the first region size then in general you will get much faster routing, and in the cases it fails, only slightly slower.</div><div><br></div><div>charles</div><div><br><div><div>On Feb 2, 2011, at 3:36 AM, Daniel Kastl wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Emre,<div><br></div><div>How large is your network?</div><div>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.</div><div>
Ride the city for example is using pgRouting and the size of the cities should be comparable to Istanbul:</div><div><a href="http://www.ridethecity.com/">http://www.ridethecity.com/</a></div>
<div><br></div><div><a href="http://www.ridethecity.com/"></a>To improve speed you can check:</div><div><ul><li>Indices for attributes used in your query</li><li>ID numbering (very high ID's make it slow)</li><li>complicated cost calculation and joins between tables. If you have this, maybe you could pre-calculate some costs.</li>
</ul><div>In general as less network data you load with your select as faster it is.</div><div><br></div><div>Daniel</div></div></blockquote></div><br></div></body></html>