Marge Bot pushed to branch master at Glasgow Haskell Compiler / GHC Commits: e841931c by Teo Camarasu at 2026-04-08T20:52:00-04:00 doc: improve eventlog-flush-interval flag documentation We mention the performance cost and how this flag can be turned off. Resolves #27056 - - - - - e332db25 by Teo Camarasu at 2026-04-08T20:52:01-04:00 docs/user_guide: fix typo - - - - - 1 changed file: - docs/users_guide/runtime_control.rst Changes: ===================================== docs/users_guide/runtime_control.rst ===================================== @@ -1331,7 +1331,7 @@ When the program is linked with the :ghc-flag:`-eventlog` option package. Each event is associated with a timestamp which is the number of - nanoseconds since the start of executation of the running program. + nanoseconds since the start of execution of the running program. This is the elapsed time, not the CPU time. .. rts-flag:: -ol⟨filename⟩ @@ -1352,6 +1352,12 @@ When the program is linked with the :ghc-flag:`-eventlog` option This can be useful in live-monitoring situations where the eventlog is consumed in real-time by another process. + Flushing the eventlog requires synchronising all capabilities, + which can be lead to performance regressions in highly parallel + applications. + + To disable this flag set ⟨seconds⟩ to 0. + .. rts-flag:: -v [⟨flags⟩] Log events as text to standard output, instead of to the View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/0a83b95b436c5a47deb07e96c45f6c2... -- View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/compare/0a83b95b436c5a47deb07e96c45f6c2... You're receiving this email because of your account on gitlab.haskell.org.