(Was reading through your article from 2014 on Syslog Perf) No thank you for the advice.. that’s one reason I’m in the list! These rsyslog servers are going to receive lots of messages from up two a couple dozen sources each so I’m really wanting the best initial config I can scope. I know tweaking will take place but I’d rather they didn’t fall flat on their faces on day 1.
The description of asyncWriting does leave an impression of a tiny but extra cpu load, but what’s unclear except from maybe years of experience, is how impactful versus the gains. From: David Lang <da...@lang.hm> Date: Monday, August 29, 2022 at 3:51 PM To: Ben Hart via rsyslog <rsyslog@lists.adiscon.com> Cc: Ben Hart <ben.h...@jamf.com> Subject: Re: [rsyslog] Error with omfile and queue.filename syntax? by the way, async writes on omfile are almost never a good idea, it adds an extra queue between the omfile module and the write, and the locking on that queue adds more overhead than the write would. The place it has some use is where your output has a significant amount of processing (compressed output for example), and even then you have to check. not the issue you are posting about, but something I noticed in the config. David Lang _______________________________________________ rsyslog mailing list https://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
