take a look at the imptcp module. My understanding is that it handles large
numbers of connections better than the plain imtcp module
I have done very high traffic volume tests with rsyslog, but have not been in a
position to test thousands of connections to one box. Rainer will need to
comment on this.
David Lang
On Fri, 14 Jun 2013, Timothy Ehlers wrote:
Is there a recommended connection count per port.
We are sending to rsyslog using syslog-ng and this was working for a while.
Suddenly syslog-ng is sending data which rsyslog is not acknowledging
(tcpdump).
We have a very high server count and were at ~3000 connections on port
20514, currently rsyslog seems to drag after ~500 connections. But it is
slowly building them back up.
Are we hitting some kind of wall?
Version info:
rsyslog-7.2.5
Ulimit info:
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 385913
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 65536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 1024
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
_______________________________________________
rsyslog mailing list
http://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.
