Profiling tools about mapbox-studio-classic HOT 4 CLOSED

Great, curious to hear your ideas. Starting really high level I think will be good - like just providing quick feedback on aggregate tile load times (maybe reporting a small sparkline of last 10 saves?) or a quick hover per tile mode. I logged more low level ideas previously at https://github.com/mapbox/mapbox-streets/issues/368

from mapbox-studio-classic.

y agreed

from mapbox-studio-classic.

I've started some experiments with this in the renderstats branch. Currently focusing on measuring render time (ie. excludes time to download/cache hit vector tiles, map compile/load time, etc.) as it's the most relevant stat for the designer to tune for.

The code so far stores min, max, and avg for tile draws. I wanted to see if this stat would yield consistent enough results to be useful. So far, it looks like yes, with max sometimes being an outlier (e.g. you start watching a youtube video while your map is loading === single max outlier).

Next question for me is how it feels to use these stats and whether they can actually be used during the design process. Would love for you guys to try it out @ajashton @ian29 @springmeyer

ps. I also briefly tried storing stats on a per-tile basis and quickly backed out. My brief notes: a lot of overhead, difficult to convey data in an actionable manner, or rather, possibly too much detail overall to be useful.

from mapbox-studio-classic.

Merged.

from mapbox-studio-classic.