As a side-note, this does not yet mean that the input module itself runs on multiple threads. So the new functionality probably works best across different inputs. Massiv-parallel inputs are on my agenda as well, but some other things need to be done first so that I will have the necessary basis to build on (I'll not use a simple "one thread per connection" model, as this does not scale well). I'll probably go for multiplexed io with potentially one queue per worker, and quick worker engagement into that queue where no wait is necessary ... but more later ;)
Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Aaron Wiebe > Sent: Tuesday, October 27, 2009 5:59 PM > To: rsyslog-users > Subject: Re: [rsyslog] important enhancement in rsyslog upcoming > > This looks like it has a lot of potential! I look forward to trying > it. > > -Aaron > > On Tue, Oct 27, 2009 at 12:53 PM, Rainer Gerhards > <[email protected]> wrote: > > Hi all, > > > > I was finally able to add some new featueres to rsyslog (stability is > still > > my priority), and I think it is a very exciting one. In short: we can > now > > partition input message into different queues, dramatically > decreasing lock > > contention potential. > > > > Please read yourself: > > > > http://blog.gerhards.net/2009/10/next-round-of-performance- > enhancement.html > > > > The change is committed, but I'll probably be busy a day or two with > lab > > testing and testbench enhancement before I continue to add more > enhancements. > > > > Rainer > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
