Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Mi 03.07.2024 00:02:07 4.687 0 255.016 54,4 PHP Community on Mastodon 4.2.9 500 Di 02.07.2024 00:01:46 4.687 +1 254.749 54,4 PHP Community on Mastodon 4.2.9 500 Mo 01.07.2024 00:02:13 4.686 +1 254.463 54,3 PHP Community on Mastodon 4.2.9 500 So 30.06.2024 00:00:00 4.685 +3 254.266 54,3 PHP Community on Mastodon 4.2.9 500 Sa 29.06.2024 00:01:27 4.682 +3 254.006 54,3 PHP Community on Mastodon 4.2.9 500 Fr 28.06.2024 00:01:14 4.679 +1 253.728 54,2 PHP Community on Mastodon 4.2.9 500 Do 27.06.2024 00:01:22 4.678 0 253.492 54,2 PHP Community on Mastodon 4.2.9 500 Mi 26.06.2024 00:00:32 4.678 +2 253.161 54,1 PHP Community on Mastodon 4.2.9 500 Di 25.06.2024 00:00:01 4.676 0 252.793 54,1 PHP Community on Mastodon 4.2.9 500 Mo 24.06.2024 00:00:14 4.676 0 252.555 54,0 PHP Community on Mastodon 4.2.9 500
Ben Ramsey (@ramsey) · 08/2018 · Tröts: 13.904 · Folger: 3.999
Mi 03.07.2024 21:20
What's the performance impact of logging in #PHP? Is there an I/O difference between writing to `STDERR` or `STDOUT` vs. a local file on disk?
I've heard folks like @rasmus speak in the past about ensuring you don't have errors because, even if you have error logging set to `error_reporting(0);` (i.e., "off"), the error handler is still invoked, so there's still a tiny a perf. hit, but I'm curious about the I/O impact between the various log streams.
[Öffentlich] Antw.: 0 Wtrl.: 1 Fav.: 0