Opened 4 years ago

Last modified 3 years ago

#1109 new enhancement/feature request

Address search is very slow on PND

Reported by: алексей черепанов Owned by: KaZeR
Priority: critical Milestone: version 0.5.1
Component: core Version: git master
Severity: normal Keywords: address, search, performance, wince
Cc:

Description (last modified by usul)

I try to use Navit on GPS navigator Texet TN 606. Street search by 3 first letters in Chelyabinsk, Russia takes at least 25 seconds. It's very slow and quite unusable.

Change History (15)

comment:1 Changed 4 years ago by tryagain

Hi!

We currently don't use indexes to do house number and street searches, only towns are indexed.

I think adding such an index will significantly increase server load which currently rebuilds the whole world map every night. And we're not going to lose that feature. Though there are still some different ways to consider.

We are working to improve it, but I do not expect to have a solution in few weeks.

tryagain.

comment:2 Changed 4 years ago by алексей черепанов

OK Would you add this feature in maptool as option for building map?

comment:3 Changed 4 years ago by tryagain

Adding street indexes is not that easy, so not right now.

You may try r5440 version, it gives me a slight perfomance benefit on my android device. Do not expect too much from that change though.

Last edited 4 years ago by tryagain (previous) (diff)

comment:4 Changed 4 years ago by алексей черепанов

Hi! And now I can't find street of "проспект Победы" in Chelyabinsk. My home place and area around is real bug check example for Navit :)

comment:5 Changed 4 years ago by tryagain

Hi!

Your street should be findable since r5443.

Also, I expect a notable performance improvement with that release. Please report your results.

comment:6 Changed 4 years ago by алексей черепанов

Hi! Now street search in Chelyabinsk takes about 15 seconds. It's a good result, thanks. But other navigation programs, such as 7 Ways or Navitel, do it in a moment. I think there is no way to make it faster but full indexing.

comment:7 Changed 4 years ago by tryagain

Hi!

There are still some ways to improve...

Please check if r5447 changes give you any benefit.

tryagain.

comment:8 Changed 4 years ago by алексей черепанов

Hi!

May be it's a little bit faster. I haven't found significant acceleration on Windows CE6 navigator.

comment:9 Changed 4 years ago by tryagain

Hi!

Please try with current svn, there should be a notable change since r5463.

comment:10 Changed 4 years ago by алексей черепанов

Hi!

Still about 15 seconds on PNA :( May be it is very low performance device, or there is lack of memory. I'll try Navit on another type PNA. It works at least 2 times faster on noname China Android phone than on PNA.

Last edited 4 years ago by алексей черепанов (previous) (diff)

comment:11 Changed 4 years ago by usul

  • Component changed from mapdrivers/OSM to core
  • Description modified (diff)
  • Keywords address search performance wince added
  • Milestone changed from version 0.5.0 to version 0.5.1
  • Owner changed from cp15 to KaZeR

Thanks for helping us on this issue :)

AFAIK 400MHz and 64MB RAM is a usual configuration for PNDs. So if we wan't to support that device class, we will still need some tweaks.

BTW, what map file are you using? (date and size?) Maybe we should try to reproduce your usecase and see, if this might be related to your hardware? (e.g. very slow SD card, background tasks, ...)

As this is an essential bug which results in a unusable Navit experience, I schedule it to the upcomming 0.5.1 hotfix.

comment:12 Changed 4 years ago by алексей черепанов

Hi, KaZeR.

I have last version of TN-606 with 128 Mb RAM. I tried to use 3 maps: Russia map downloaded from Navit map server about 880 MB, Russia map made with maptool from OSM data about 650 MB, and Chelyabinsk region map made with maptool from OSM data about 17 MB. With 1st and 2nd map I got result described above. With 3rd map it was about 25% faster. Maps were created in April 2013. I tested Navit with this 3 maps on other PND with 550 MHz Atlas-V CPU and 128 MB RAM (Explay PN-945) and got similar result. Program and maps were placed in internal flash memory in both cases.

comment:13 follow-up: Changed 3 years ago by tryagain

  • Severity set to normal

alxchr,

I've fixed an issue with wrong objects being placed into the root tile of navit binfile map. Please retry with a recent map (dated since the 9th of December, 2013). You may get a difference.

comment:14 Changed 3 years ago by usul

  • Priority changed from major to critical

I suggest to increase the priority of this issue, as 0.5.1 is about to deploy a stable and rough usable release. So Responsiveness is a very basic requirement to endusers, otherwise Navit appears to be broken.

comment:15 in reply to: ↑ 13 Changed 3 years ago by алексей черепанов

Replying to http://wiki.navit-project.org/index.php/user:tryagain:

alxchr,

I've fixed an issue with wrong objects being placed into the root tile of navit binfile map. Please retry with a recent map (dated since the 9th of December, 2013). You may get a difference.

I see no significant change in performance, was 25 sec, now is still about 15 sec at the same device.

Note: See TracTickets for help on using tickets.