-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix GC stats. #48
Fix GC stats. #48
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lib/olly_gc_stats/olly_gc_stats.ml
Outdated
let wall_time = { start_time = 0.; end_time = 0. } | ||
let total_cpu_time = ref 0. | ||
|
||
let domain_cpu_times = Array.make 128 (0.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is 128 still the maximum number of domains we can create at a time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
128 is still the default. There is an option in 5.3 to increase the number of domains with the help of an OCAMLRUNPARAM parameter: #48. However, there is no way to get this number out programmatically. Perhaps there should be a Domain.max_domain_count
similar to Domain.recommended_domain_count
. Once we have that, we can replace 128 with the result of that.
Use wall clock time for per-domain time calculation.
Needs more fixes. We should be using the timestamp from the event not the one using |
Use wall clock time for per-domain time calculation. This is better than using CPU time.
If a core spends 98 s doing io, 1 s doing computation and 1 s doing GC, the GC overhead should be 1%.