You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That would be awesome if we could get it into the data source side. We need to do more profiling, but sadly I think our bottlenecks are in the data connectors rather than our renderer.
On Sun, May 12, 2013 at 10:03 PM, Rob Brackett [email protected]
wrote:
FWIW, the biggest time-sink at the moment is, surprisingly, turning colors (from Carto's AST) into strings! That one is definitely renderer-side. There's also a huge amount of Array.forEach() use in the renderer, which is known to be slow (both for JS/C++ re-entry and for call frame creation). Don't remember off the top of my head what the other standout issues were when I was experimenting with node --prof (which is not friendly) about a month ago.
That would be awesome if we could get it into the data source side
Also not really sure whether it would belong on the source side or whether the options should be specified via the style sheet (which seems to be a more natural fit, though harder technically to make work).
Ran across this library the other day: https://github.com/mourner/simplify-js
Could potentially use it to add line simplification as a feature. Not sure how valuable it would be (or the right way to expose it to use).
The text was updated successfully, but these errors were encountered: