From issue 617111#8: vmiura@chromium.org:

Here is a trace running on Pixel C, which uses the path rendering extension.  I enabled full command tracing (Service.TraceCmd) which makes everything ~50% slower, but the bottlenecks don't change.  It's spending all the time in the path rendering extension.

 kStencilThenCoverFillPathCHROMIUM  198.291 ms 198.227 ms 0.000 ms 0.000 ms 2735
 kDeletePathsCHROMIUM                55.143 ms  52.846 ms 0.000 ms 0.000 ms 2628
 kPathCommandsCHROMIUM               25.958 ms  26.445 ms 0.000 ms 0.000 ms 2628
 kDeleteBuffersImmediate              1.310 ms   1.312 ms 0.000 ms 0.000 ms    3
 kDrawElements                        1.208 ms   1.250 ms 0.000 ms 0.000 ms   99 
 kScissor                             0.697 ms   0.719 ms 0.000 ms 0.000 ms  144

	trace_svg-test-chalkboard-pixel-c.json.zip 


The test suffered from path cache trashing.

Investigate GPU rasterization of path-heavy content on Pixel C.
Verify whether the performance is better or worse by enabling NV_path_rendering.