[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#435884: ITP: rsyslog -- enhanced multi-threaded syslogd

On Sun, Aug 05, 2007 at 10:25:34PM +0200, SZALAY Attila wrote:
> And yes, I know that the choosen method is depend on the function. But I
> think that this function is better to implement with multithread than
> multiprocess, because:
> 1. Reading a log message and write it to a file is highly paralellable.
> 2. There may be a lot of paralell reading. (the config)
> 3. We have to ballance the load about message, not connection because
> sometimes a small number of programs (maybe one) generate a big part of
> messages.

Since messages arrive on a single socket (usually connection-less)
ultimately the messages enter through one process/thread. And they get 
written to a file or database which is ultimately not parallelable
either. Is there a huge amount of processing in between which justifies

Also does rsyslog guarantee that messages are logged in the order they
are sent? If messages may take different paths due to multi-threading I
guess this would need extra care.

> And I think that the real question is that there is place in Debian for
> a multithread/process system logging daemon (against the singlethread
> ones) or not. And I think that this dispute is onlt theoretical. :)

My original question was why you would mention multi-threaded in the
short description of rsyslog?

Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Reply to: