3 ms·

In which case, what on Earth is rsyslog doing that it takes 1ms to append a line of text to the log file? I could see it if it was outputting something to soft

• JoachimSchipper 11y ago
  You need quite a few kernel<->userland switches in this case, maybe that's enough?
  • TheLoneWolfling 11y ago
    Potentially, although in that case it's still dsyslog's fault.
    • ars 11y ago
      It's classed as an ALERT level message, so rsyslog will sync after outputting it. That might account for the time.
• simoncion 11y ago
  > ...except that in that case, why is it trying to output to software-based video? I don't have much experience with rsyslog, but syslog-ng can be configured to log to all consoles. [0] I know that consoles are usually configured to blank themselves after a period of inactivity. I wonder if a blanked console can be written to faster than an non-blanked one. [1] Edit: The Fine Article supports my assumption about how rsyslog is configured on the RPi. Search for "printk". Also remember that -when syslog is disabled- printks are written to the active console. [0] The default configuration appears to log everything to /dev/tty12. I see no reason why you couldn't log everything to -I guess- /dev/console. (Or, failing that, /dev/tty[0-12].) [1] I know that screen-scrolling updates that happen in a console that is not the current one (or that happen in a screen window that's not the current one) are substantially faster than on-screen screen-scrolling updates.