Marcelo wrote: > On Oct 19, 7:47 pm, pps <[email protected]> wrote: > >> In my implementation and yours if I drag around polygon I see >> 100% cpu load taken by the browser. I really don't care about that 100% >> cpu problem, but to me it means that something should be done >> differently/properly. > > Your computer must be old. > In my Core 2 Duo 2.26 GHz it doesn't even get to 50%. :-) >
Well, my pc is cooler than your outdated core2 duo. On my 4 cores I don't even get 25% :) The point is that it takes 100% of a core, to me it's the same as 100% cpu. When we have 8 core cpus any malfunctioning program that gets stuck in an infinite loop will be barely noticeable, since it won't take over 12.5% of total cpu power, but it doesn't mean that everything is OK. Same for draging polygons around. If you add semitransparent png on top of Gmap and drag it around (without ever attaching it to gmaps, just a separate draggable image that floats on top of gmaps) will you have 100% on a core? That's the point: draging a polygon shouldn't be insanely heavy task. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
