It is a historical artifact that Tenuring data is handled outside of the GC cycle that is reporting on it. This was to more easily facilitate the parsing of pre-unified log files which suffered from corruption due to multiple threads updating the log at the same time.
This threading issue has been resolved with unified logging. Also unified logging has simplified the parsing process. Thus it is past due that this artificial separation be remove.
Given that this will be a breaking change, the tenuring information will first be added to the appropriate GC events. The Tenuring events will still be produced separately. After some time, the Tenuring events for Unified logging will be removed. For older logs the parsing and reporting of tenuring information will remain the same.
It is a historical artifact that Tenuring data is handled outside of the GC cycle that is reporting on it. This was to more easily facilitate the parsing of pre-unified log files which suffered from corruption due to multiple threads updating the log at the same time.
This threading issue has been resolved with unified logging. Also unified logging has simplified the parsing process. Thus it is past due that this artificial separation be remove.
Given that this will be a breaking change, the tenuring information will first be added to the appropriate GC events. The Tenuring events will still be produced separately. After some time, the Tenuring events for Unified logging will be removed. For older logs the parsing and reporting of tenuring information will remain the same.