P3 Description
The ParallelGC has logging in debug builds (even if it is guarded by a product flag) that logs messages for each task.
The output from this logging i pretty scrambled and hard to make sense of. See the attached gc.log file for an example. Each thread prints the task it is currently working on. There is no correlation between threads and there is no summary to add times for related tasks.
This type of per thread information is hard to make useful in a log file. It would be much better to add trace events for this information.
Rather than trying to fix this logging we should remove it. If it turns out that it is needed in the future we should add trace events to track it.
The output from this logging i pretty scrambled and hard to make sense of. See the attached gc.log file for an example. Each thread prints the task it is currently working on. There is no correlation between threads and there is no summary to add times for related tasks.
This type of per thread information is hard to make useful in a log file. It would be much better to add trace events for this information.
Rather than trying to fix this logging we should remove it. If it turns out that it is needed in the future we should add trace events to track it.