rendering time reporting events

[justadreamer]

Is your feature request related to a problem? Please describe.
We made a patch fixing some markup issues in the PUC on mobile, it may impact rendering times performance, however there is no easy time to measure the rendering time without instrumenting the PUC with logging calls. We also need the baseline to test against.

Describe the solution you'd like
We would like an event sent into the native layer we could subscribe to and receive the start of rendering and end of rendering. This is mobile specific - so the mechanism to message might be GAM App Events and native layer to subscribe. The native layer will receive the events and me

Describe alternatives you've considered
We considered logging via console.log, but it is hard to capture console logs on mobile and then track analytics based on those logs.

Additional context
The idea is to track prebid.puc_render_begin and prebid.puc_render_end events and then in the native layer we can measure time difference between those and record in this metrics.

[ValentinPostindustria]

It seems that the two events, prebid.puc_render_begin and prebid.puc_render_end, don't work well for measuring rendering time. Sometimes the Google SDK triggers both events at the same time, resulting in a difference of only 2–3 ms, while the actual rendering time measured from the JS code is more than 100 ms.

JS rendering time: 115.595947265625 ms
Native rendering time: 3 ms

Therefore, we decided to keep only one event with the key puc_render_time and a value representing the rendering time in milliseconds.

[YuriyVelichkoPI]

@justadreamer , @ValentinPostindustria Is this issue still relevant?