On Wed, Oct 8, 2008 at 6:45 PM, Lambertus <[EMAIL PROTECTED]> wrote: > > The website (YOURS) and the route calculation application (Gosmore) run > on an (already beefy) sponsored server so any speedup gain should be > made with better or smarter code. I don't currently know of any other > routing application that can handle the OSM data as well as Gosmore does. >
The bottleneck with gosmore routing a.t.m. is that hashing business. Sometimes it allocates way too much memory, resulting in "thrashing" and cache misses. I always guessed that the only way to get rid of of the hashing, would be to have like 20GB of RAM. But after this thread, I invented a new way of doing it that uses a more dynamic way of memory allocation. So I implemented it, but could not see any difference with the 26MB South African gosmore.pak file. If someone (Lambertus) wants to try it out on a larger .pak file, here are some pointers : * Check out of SVN * make CFLAGS="-O2 -DROUTE_SRV" * On 32 bit machines it will only work with smaller .pak files, say smaller than 500MB. 64 bit machines should have no limit and may just be able to route from NY to LA in a reasonable time. * Potentially needing a lot of free disk space. See tmpfile() Regards, Nic
_______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
