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
I'm currently doing some perf work on gl-draw and found that the call to setData for a geojson source takes ~6milli on average when calling it with an object. I haven't checked what happens when you call it with a url.
Because this api can take a url, I assumed it was an async function that did its hard work on its own time. Should setData be async? If so, I can dive in and find out why its not. If not, I can work around this in gl-draw, I just wanted to check.
Also, the length of time this function takes from a synchronous point of view is all over the place even if the geojson object is more or less the same size.
The text was updated successfully, but these errors were encountered:
It is async, in that it transfers data to a web worker for processing. But passing a lot of data to a web worker is inherently expensive, which is why we recommend using a URL.
I'm currently doing some perf work on gl-draw and found that the call to setData for a geojson source takes ~6milli on average when calling it with an object. I haven't checked what happens when you call it with a url.
Because this api can take a url, I assumed it was an async function that did its hard work on its own time. Should setData be async? If so, I can dive in and find out why its not. If not, I can work around this in gl-draw, I just wanted to check.
Also, the length of time this function takes from a synchronous point of view is all over the place even if the geojson object is more or less the same size.
The text was updated successfully, but these errors were encountered: