We are using Boomernang JS for our RUM instrumentation. It works well when http.initiator == spa_hard
. However, when measuring http.initiator == spa
(ie. soft loads) we will often see values for t_done
(page load times) being in the area of 1000000ms, which is definitely inaccurate.
On top of that, even though t_done should be rt.end - rt.t_start
, we will see often very large values for t_done
yet rt.end == rt.t_start
- the start and end values are equivalent as shown in this example:
{
"pid": "7dv9jmse",
"rt.bstart": 1604083165272,
"rt.end": 1604411098690,
"rt.nstart": 1604083161590,
"rt.obo": 0,
"rt.sl": 0,
"rt.ss": 1604083161590,
"rt.start": "manual",
"rt.tstart": 1604411098690,
"rt.tt": 0,
"sm": "i",
"t_done": 429144,
"t_page": 422485,
"t_resp": 6659,
"u": "RETRACTED",
"vis.lh": 2374175,
"vis.lv": 20978,
"vis.st": "visible"
}
Has anyone had encountered issues with SPA timing on Boomerang in the past. We are using Angular.
There have been several bug fixes, and updates made to bow BOOMERANG handles SPA Soft requests over the last year. Please see the release notes to determine if the version of BOOMERANG you are using contains the latest revisions: https://developer.akamai.com/tools/boomerang/release-notes
In particular look at the following:
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.