GitLab

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
```

@@ -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