September 07, 2018 [Issue 18388] std.experimental.logger slow performance | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=18388 --- Comment #11 from Arun Chandrasekaran <aruncxy@gmail.com> --- s/_logger.tracef/writeln 06-09-2018 20:05:27 vaalaham ~/code/d/std-log-benchmark $ time ./std-log-benchmark 8 1000000 | tail real 0m0.975s user 0m2.067s sys 0m2.418s 06-09-2018 20:05:29 vaalaham ~/code/d/std-log-benchmark I can infer that std.format is probably a little slower than fmtlib (C++) https://github.com/fmtlib/fmt But I need to test more to confirm this claim. But for sure std.experimental.logger is slow. -- |
September 07, 2018 [Issue 18388] std.experimental.logger slow performance | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=18388 --- Comment #12 from Robert Schadek <rburners@gmail.com> --- Building the string in memory will put quite some pressure on the GC. Using a stack based array is limiting and not @safe. formattedWrite can do more than printf. I stayed away from allowing configurations, because it is really hard to know what should be a config option and what not. So the idea is to inherit and change in code what need to be different. -- |
December 18, 2018 [Issue 18388] std.experimental.logger slow performance | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=18388 Arun Chandrasekaran <aruncxy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |LATER --- Comment #13 from Arun Chandrasekaran <aruncxy@gmail.com> --- Closing as of now as per the last comment - we can reopen in future if required. -- |
Copyright © 1999-2021 by the D Language Foundation