search

OsmSharp / ui

The UI components.
http://osmsharp.com/
GNU General Public License v2.0
138 stars 91 forks source link

Search runs perpetually #159

Closed JoeCooper closed 10 years ago

JoeCooper commented 10 years ago

With version 4.2.0.809, I run a search for two given points which both resolve correctly and the search seems to run perpetually. I am using a router file generated with an updated OsmSharpDataProcessor built and run with the same OsmSharp version. Is it possible that it's simply taking a very long time? I don't know how much data I can reasonably give it.

xivk commented 10 years ago

Routing should perform pretty well except on some low-end mobile devices and when the area is too big for the devices to handle.

Same note as in the other issue about the daily builds.

JoeCooper commented 10 years ago

When should we expect the next stable release?

On Aug 15, 2014, at 11:09 AM, Ben Abelshausen notifications@github.com wrote:

Routing should perform pretty well except on some low-end mobile devices and when the area is too big for the devices to handle.

Same note as in the other issue about the daily builds.

— Reply to this email directly or view it on GitHub.

JoeCooper commented 10 years ago

I have new details. I tested the same application with the latest OsmSharp with two different router files; one produced a month ago (by you) and one produced just now with OsmSharpDataProcessor built with the latest OsmSharp. The problem does not manifest with the prior file; routes are found nearly instantly. The latter file, which is slightly larger for some reason, takes overwhelmingly longer. I can send you both data files and a route to test with and I bet there's a bug in there. Shall I?

xivk commented 10 years ago

I hope to release this week. I'm running some more tests now to see if everything is still working as it should and the new features are stable.

JoeCooper commented 10 years ago

"when the area is too big for the devices to handle."

Can you give some idea of what that means? We have a router file covering one state that weighs just under 40 megs, and it takes a real long time to find a route on the desktop.

xivk commented 10 years ago

Are you using the files for mobile? If not it's best you just load the graph in memory, one state shoudn't be a problem.

I also noticed some performance problems with big routes on mobile. This is planned for the next couple of weeks.

JoeCooper commented 10 years ago

I'm using the graph file built for mobile. I tried using a live router (if that's what you mean) and it failed on mobile; out of memory. I also tried using the graph for mobile and loading it to RAM and providing the kit with memory streams but this didn't help at all.

JoeCooper commented 10 years ago

I'm no longer able to reproduce perpetual searches. Thanks! (To be clear it's still pretty slow for me but I'm not considering that part of this ticket.)