Re:The logging framework isn't a bottleneck, and other lies ...
by steerablesafe on Thursday May 14, 2020 @04:22AM
(#23176901)
There is a significant difference between "works everywhere" and "works everywhere efficiently". For the former you can get away with just writing portable code. For the latter you basically have to benchmark everywhere. Performance is a hell of a leaky abstraction.
[ Parent
| on HN ]
Re:The logging framework isn't a bottleneck, and other lies ...
by fetbaffe on Thursday May 14, 2020 @04:35AM
(#23176995)
Yes, that is why it is futile to try to have an exact copy of the production server because the smallest difference will ruin your performance profiling, to be absolutely sure you have to do the profiling on the production server itself.
Usually every developer has their own login user on the development machine, but that is enough to skew performance profiling, because usernames populates environment variables & that will change memory layout of any program that the shell executes.
Re:The logging framework isn't a bottleneck, and other lies ...
by steerablesafe on Thursday May 14, 2020 @06:07AM
(#23177637)
If memory layout changes due to environment variables significantly changes performance characteristics then it looks like an opportunity to optimize this aspect of loading a binary. I assume cache alignment is in play here.
Re:The logging framework isn't a bottleneck, and other lies ...
by fetbaffe on Thursday May 14, 2020 @07:54AM
(#23178384)
Good video on the topic
Re:The logging framework isn't a bottleneck, and other lies ...
by steerablesafe on Thursday May 14, 2020 @10:19AM
(#23179831)
Thank you, this is a fantastic talk.
It's great that they can average out the random effect of layout, but what I meant by optimization opportunity is to deliberately aim for the "good" memory layouts. Something like fixing the alignment of the stack on program entry point or marking specific functions as "stack aligned".