I guess your problem is rooted in name resolution. A full blown DNS cache has only recently been introduced in v6. Previous version had limited caching, which usually works well, but not in all cases. Also 4.2.0 is *way outdated*, so probably the issue (if it is one rooted in code) may be solved by running the current 4.8.6 version.
HTH Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Gaurav Kumar > Sent: Thursday, January 12, 2012 9:40 AM > To: [email protected] > Subject: [rsyslog] udp forwarding performance > > Hi all, > I am wondering if anybody has performance testing numbers for rsyslog > forwarding (using UDP) ? > > Currently, I am forwarding all of my rsyslog messages from one host to > another host (also running rsyslog). Both hosts are running version > 4.2.0. > I am seeing throughput of about 2k-3k messages/second on receiver. If I > try > to send more messages from sender, I find that receiver's rsyslog is > dropping logs. Both hosts share same virtual network with network > latency > of just about 1-2 ms. Both hosts have 2 virtual CPUs and 2 GB RAM. > > As per http://blog.gerhards.net/2008/10/rsyslog-performance.html it > seems > that rsyslog is capable of performing processing 100k messages/second. > > Can someone please clarify that this number (100k) is for local syslog > messages only? (as opposed to receiving 100k messages/second over > network) > > My intent is to find out what is the expected number of messages that > rsyslog can forward to other rsyslog host? (assuming average host spec- > dual core, 2 GB RAM) > > Cheers, > Gaurav > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
