On Dec 8, 8:09 pm, John Mick <[email protected]> wrote:
> Hey sorry for the delay - I ended up getting pretty sick over the
> weekend and haven't been back into the office until today.
>
> I was all setup to run your test on Friday under IE8 - Chrome - and
> Firefox, but the interval on calling Cycle was changed from the
> previous 3 seconds to 0 ms. Opening the test in those 3 browsers
> (each full-screen on one of 3 monitors) had my CPU usage hanging out
> at around 60%+. I didn't really want to tax the work machine that
> badly over the weekend so I elected to not run the test.
Feel free to make changes to the test case. I was trying to compare
CANVAS, SVG & VML rendering speeds.
> Anyhow I am glad that our discussions helped you find some ways to
> improve your library - it is a very impressive.
>
> I definitely recommend using SVG as a default over CANVAS. Though
> both SVG and CANVAS require the browser to render the individual
> pixels when they are displayed - CANVAS, being bitmap based, has to
> store a value for what it is that it is going to draw on every point -
> unlike SVG which uses a more mathematical vector approach. In testing
> - I found that very very very large CANVAS objects took significantly
> more memory to render than SVG objects of the same size.
For dragging, panning & zooming, CANVAS is much quicker. But CANVAS
does not support mouse events. If a browser supports both, the choice
depends on whether event listeners are specified.
You can see the performance differences at:
http://www.polylib.us
if you choose the experimental "United States" demo. Toggle
"Clickable - true" / "Clickable - false" to switch between SVG &
CANVAS respectively.
> I also found that increasing the scale of an SVG object doesn't
> necessarily increase the memory usage - if we are only talking about
> rendering - when the SVG object falls outside of the viewpoint of the
> browser itself (if the object was being drawn off-screen).
>
> I am going to continue working on tweaking my own custom solution -
> which overlays very large SVG objects over the map once - then alters
> those objects directly whenever data changes, instead of deleting and
> re-creating new ones. Time to refresh my memory on how to embed those
> VML script and namespace tags.
Are you making progress ? I will be happy to help.
> Thanks again for your help as well - it feels significantly better
> knowing that somebody else out there has some real experience with
> problems like this. (I've felt so alone for awhile! Haha)
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
