On Saturday, 6 September 2014 at 19:41:54 UTC, Kevin Lamonte
wrote:
On Wednesday, 3 September 2014 at 13:13:31 UTC, Ola Fosheim
Grøstad wrote:
Since we are talking about performance, I did some tests and
found to my surprise that ~95% of the time consumed in a log
call is Clock.currTime's call to clock_gettime(). I submitted
a report for it
(https://issues.dlang.org/show_bug.cgi?id=13433), but it also
brings up how to expose it in the std.logger API.
that is with all likelihood a syscall, so there goes your
performance
The API automatically grabs thisTid and Clock.currTime during
construction of the LogEntry (plus it should also grab
Thread.getThis and Fiber.getThis). Should this behavior be
modifiable by clients, by subclasses, or neither? If so, how?
yes, I will move some of it into beginLogMsg
