The UMA sampling profiler shows that the call of localtime_s by logging::LogMessage::Init forces the load of a supporting library via an eventual call to GetTimeZoneInformation. This is expensive, and responsible for 3.6ms of startup time on average for a recent Win x64 canary, 1.5ms of which occurs before message loop start: https://uma.googleplex.com/p/chrome/callstacks?sid=27da52168b9ee1b728f6d5009bb2d705
We should remove unnecessary logging from startup to defer this overhead as long as possible.
Comment 1 by bugdroid1@chromium.org
, Oct 13 2016