This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] [HTTP measurements] Units of timing?
- Previous message (by thread): [atlas] [HTTP measurements] Units of timing?
- Next message (by thread): [atlas] [HTTP measurements] Units of timing?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Jun 26 12:45:17 CEST 2024
Hello again, According to the documentation (https://atlas.ripe.net/docs/apis/result-format/#version-5000) those fields are in milliseconds. I believe this to be correct; your referenced measurement uses resolve-on-probe: false, therefore the DNS resolution is done at specification time and it's a no-op on the probe. Indeed On Tue, Jun 25, 2024 at 3:41 PM Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote: > > When using "extended_timing" with HTTP measurements, in what units are > tt*? > > I suspect that ttr is in seconds and the other two in milli-seconds but > I want to be sure. > > (The Web interface does not display these values, it seems, but see > measurement #74293060 if you want an example.) > > -- > ripe-atlas mailing list > ripe-atlas at ripe.net > https://mailman.ripe.net/
- Previous message (by thread): [atlas] [HTTP measurements] Units of timing?
- Next message (by thread): [atlas] [HTTP measurements] Units of timing?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]