<p dir="ltr">Yup. All of them use an independent thread. Even with threading disabled, as we are using a synchronous api to redis.</p>
<div class="gmail_quote">On Apr 28, 2015 2:34 PM, "Jim Hendrick" <<a href="mailto:jrhendri@roadrunner.com">jrhendri@roadrunner.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Could someone help clarify something for me?<br>
<br>
I am running with threading enabled, and I have separate redis<br>
destinations (three currently) all pointing to the same server. My<br>
thought was that each destination would use a separate connection and<br>
thread.<br>
I then filter log sources and send (roughly) 1/3 to each destination.<br>
<br>
My question is this. Does each destination get a separate thread?<br>
(reading the documentation it left room for doubt).<br>
<br>
Also - more generally is this a reasonable way to get better throughput<br>
to a redis data store?<br>
<br>
(note: both syslog-ng and redis are running locally, so the connections<br>
use 'localhost')<br>
<br>
Thanks!<br>
Jim<br>
<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
</blockquote></div>