Cyril SCETBON <scetbon at echo.fr> writes:
> I've got a lot of updates (~1000 w/s) on the master and on the nearest
> slave (like others) I've got a big replication lag. It seems that
> fetching lines from the cursor is not taking much time, but processing
> events is not well managed.
>
> Here you can find an extract of the log that shows that the proposed
> size for grouping is often just 3 and not greater :
>
> http://pastebin.com/f2a2974a
>
> The slon parameters used are : -g 1000 -o 0
>
> Any idea to speed up the processing ?

There's something a bit confusing in the logs; it's not affecting how
the grouping is actually working.  The "just 3" looks to be when it's
evaluating sync grouping for events coming from *other* nodes than the
provider, which is pretty much irrelevant since those syncs don't lead
to any actual work.

Looks to me like the processing of data from node #1 is working out
about as can be expected on a node that is processing a lot of data.
There may be relevant/material improvements to handling of this in
2.0; I don't think there's anything to be done in terms of
configuration.
-- 
select 'cbbrowne' || '@' || 'linuxfinances.info';
http://cbbrowne.com/info/lsf.html
Rules  of the  Evil Overlord  #145. "My  dungeon cell  decor  will not
feature exposed pipes.  While they add to the  gloomy atmosphere, they
are good  conductors of vibrations and  a lot of  prisoners know Morse
code." <http://www.eviloverlord.com/>