Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Components
Assignee
Shamser AhmedShamser AhmedReporter
Gavin HallidayGavin HallidayPriority
MinorCompatibility
MinorFix versions
Pull Request URL
Details
Details
Components
Assignee
Shamser Ahmed
Shamser AhmedReporter
Gavin Halliday
Gavin HallidayPriority
Compatibility
Minor
Fix versions
Pull Request URL
Created March 7, 2019 at 1:06 PM
Updated August 5, 2019 at 11:06 AM
Resolved August 5, 2019 at 11:06 AM
I think this is present so that if log messages are serialized to a central location it is possible to distinguish which process/slave they came from.
That functionality isn't currently being used, and there is an overhead from initialising the field. So it could be removed, or the initialisation could be commented out.
It would be instructive to trace the work involved in logging a message to check there aren't any other unnecessary bottlenecks - e.g. cloning strings etc. Maybe it would be better to create the message, and then format the string directly (but cleanly).