Is V3 slower V2???

[123gotoandplay]

Hi all,

I am converting my maps form v2 to v3 but i notice v3 is a whole lot slower. am i correct? do you have some similar experience?

regards

[geoco...@gmail.com]

On Jul 22, 11:00 am, 123gotoandplay <wesweatyous...@gmail.com> wrote:
> Hi all,
>
> I am converting my maps form v2 to v3 but i notice v3 is a whole lot slower.
> am i correct?

The design goals as I understand them for v3 were to make it smaller
and quicker than v2 (mainly to make it usable on mobile browsers).

I haven't seen any obvious performance degradation with v3, but I
haven't done any testing real performance testing either.

Perhaps you could share the two pages you are comparing so you can get
some feedback.

A lot of the "built-in" functionality of v2 was left to the developer
to implement, so it is possible that your implementation could be
optimized as well.

> do you have some similar experience?

No.

-- Larry

>
> regards

[en4ce]

its all about the map size, map size of 1920*1080 and bigger need some
times to load but overall V3 is way faster then v2

On 22 Jul., 17:22, "geocode...@gmail.com" <geocode...@gmail.com>
wrote:

[Derek Tonn]

Until Google properly optimizes all those .png tiles used in Maps, once
and for all, V3 and V2 are *BOTH* slow.

I've tried to talk with people at Google for 2+ years about
that...showing them live before-and-after comparisons that could shave
25-30% off their image tile sizes without changing their appearance
on-screen whatsoever. About as far as I ever got with them, besides a
condescending pat on the head and a few "that's nice" comments, was
talking with one of the lead persons on the StreetView project.

For a company that touts its "green" solutions though, Google sure does
waste terabytes of bandwidth in its Maps product for no good reason.

Sorry for the rant.

Derek

[Pil]

Presumably not for the guys at Google and all those that are using
brand new hardware. They won't notice any difference to the
disadvantage of v3.

v2 loads definitely faster than v2. But this seems a onesided boost
because performance after loading is quite slower and partially
sluggish.
Try to check out v2 and v3 side by side if you'll notice the sluggish
dragging of v3.

http://www.wolfpil.de/v2-v3-sidebyside.html

Thats the reason why Google Maps uses lots of v2 code because the
official Google Maps page shouldn't perform that sluggish.