No announcement yet.

Performance issues with Placemarks drawing SVGs

  • Filter
  • Time
  • Show
Clear All
new posts

  • Performance issues with Placemarks drawing SVGs

    We are currently experiencing a weird issue when having WWW draw SVGs as placemarks. Previously we had one regular SVG element that contained paths in it. To optimize some things we merged a few SVGs together using valid syntax of an SVG inside of another SVG element. But when we did this we observed horrible memory performance when WWW would try and draw more than 2000 placemarks with these merged SVGs, to the point where the memory consumption gets so much chrome crashes.

    Is there anything from a WebGL perspective that could cause this? Or maybe in WWW code? We have started digging through the WWW code but haven't found anything yet.

  • #2
    We had a GL memory problem when moving polygons. To fix it we have to manually remove old items from the gpuResourceCache similar to this: wwd.drawContext.gpuResourceCache.removeR esource(cacheKey);
    You might want to look there also, as that might also be what is going on with your Scalable Vector Graphics (SVGs).

    You might also want to simply try upping the gpuCacheSize like this:
    WorldWind.configuration.gpuCacheSize = 250e7; //It is originally 250e6 I think. So, the 7 makes it 10 times bigger which for our needs was fine and now we can load a bunch of Colladas without running out tile image GPU memory.