High level suggestion: I think it would make sense to print one or two
decimal
places for all of the timings in --trace-gc-nvp which would increase
precision
of our automated measurements, but I am not sure if all scripts that parse
that
output can cope with such a change ATM.
On the other hand I am not sure if --trace-gc really needs that high of a
precision, since it is mainly intended to be read by humans and there the
millisecond granularity is good enough. WDYT?
https://codereview.chromium.org/12209090/diff/1/src/heap.h
File src/heap.h (right):
https://codereview.chromium.org/12209090/diff/1/src/heap.h#newcode2187
src/heap.h:2187: float max_gc_pause_;
IMHO, this should actually use double precision as all the other
floating-point millisecond-based timing counters use that as well.
https://codereview.chromium.org/12209090/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
