<font size="2"><font face="tahoma,sans-serif">charles:</font></font><div><font size="2"><font face="tahoma,sans-serif"><br></font></font></div><div><font class="Apple-style-span" face="tahoma, sans-serif">I was thinking that also and it seems a good solution.</font></div>
<div><font class="Apple-style-span" face="tahoma, sans-serif"><br></font></div><div><font class="Apple-style-span" face="tahoma, sans-serif">Daniel:</font></div><div><font class="Apple-style-span" face="tahoma, sans-serif"><br>
</font></div><div><font class="Apple-style-span" face="tahoma, sans-serif">my network is just about the same as newyork. (~297k link) I do not use join tables and use precalculated cost columns. </font></div><div><font size="2"><font face="tahoma,sans-serif"><br clear="all">
</font></font>/emre<br>
<br><br><div class="gmail_quote">On Wed, Feb 2, 2011 at 4:04 PM, Charles Galpin <span dir="ltr"><<a href="mailto:cgalpin@lhsw.com">cgalpin@lhsw.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">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><font color="#888888"><div>charles</div></font><div class="im"><div><br><div><div>On Feb 2, 2011, at 3:36 AM, Daniel Kastl wrote:</div><br><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/" target="_blank">http://www.ridethecity.com/</a></div>
<div><br></div><div><a href="http://www.ridethecity.com/" target="_blank"></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></div></div><br>_______________________________________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
<br></blockquote></div><br></div>