Have a look at how it is done in iOS. There you can have as many annotations as you want, and the system will only render the associated markers if they are actually on screen. In addition you want to limit the number of visible markers when you zoom out. Generally anything over 50 will be illegible on a phone screen. So have a round robin buffer of 50 annotations that you update based on the proximity to your current map center.
On Tuesday, November 5, 2013 12:09:29 AM UTC-5, raj wrote: > Hi, > > I am looking for ideas to tackle a memory issue that I face with Google > Maps for Android API v2. > My application requires loading thousands of markers (20k or 40k etc). In > testing with 10k markers, i see that the map gets loaded in 20secs, which > for now is okay. > > but the problem is that the user can go back to a different activity and > return to the map activity(with a filter), at which point i need to load > say 5k markers(could be different). But this time the GC is called and it > might take upto 10 mins to load 5k markers. > > Can someone provide me some ideas to tackle this? I do need to show all > markers. > > Best, > R > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
