Different output in console.timeEnd between engines

[sant123]

let obj = {}, map = new Map(), n = 1000000;

for (let i = 0; i < n; i++) {
  obj[i] = i;
  map.set(i, i);
}

let result;
console.time("Object");
result = obj.hasOwnProperty("999999");
console.timeEnd("Object");

console.time("Map");
result = map.has(999999);
console.timeEnd("Map");

This is what Deno prints:

This is what Node.js prints:

This is what Google Chrome prints:

What I see is Node.js and Google Chrome print the result in decimal but Deno is rounding the number. I'm curious if this is expected?

Thanks.

Source - https://bretcameron.medium.com/how-javascript-maps-can-make-your-code-faster-90f56bf61d9d

[kitsonk]

It should be noted that high resolution time is not available by default in Deno due to security issues and requires a permission flag. But console should log the partial ms if available, IMO.

[comunidadio]

Even with -A option, and with performance.now() returning with precision, console.time is still limited to millisecond precision.