[android-developers] Re: memory issue with Google Maps API v2

2013-11-15 Thread raj
Thanks Everyone for the reply. We are stress testing our app. We do it in 
all platform and seems like Android has a poor performance(or my 
implementation is poor). We do not do any special thing for iOS, but the 
all the 20/40K markers are rendered within 5-10 secs. Now I agree that the 
A6 chip can have better performance than the Qualcomm ones(i read an 
article about how that Samsung will boost its clock speed when it detects 
any benchmark apps).
Leaving that aside, I have done everything that the Google IO talked about 
memory management, and not sure where I am wrong(or what am missing).

On another note, If say i am using the app for sometime(to create lot of 
objects) and then connect the device to DDMS and 'cause  GC', i see that it 
works fine, which means that those objects could have been collected. But 
the system is not able to collect them automatically. Any ideas?

R

On Tuesday, 5 November 2013 00:09:29 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.


Re: [android-developers] Re: memory issue with Google Maps API v2

2013-11-05 Thread Mukesh Srivastav
Not sure about your actual requirement of placing thousand's of marker, as
far i implemented, I have considered a radius based marker, like searching
for Hotel,fuel stations in a radius of 10 miles or 5 miles.


On Tue, Nov 5, 2013 at 6:07 PM, lbendlin  wrote:

> 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.
>



-- 
Warm Regards,
*Mukesh Kumar*,
Android Consultant/Freelancer,
India,Hyderabad.

-- 
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.


[android-developers] Re: memory issue with Google Maps API v2

2013-11-05 Thread lbendlin
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.