chris wrote:
Cyril SCETBON <[EMAIL PROTECTED]> 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.
you mean it does not consume time ?
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.
grouping does not mean using bigger transactions to apply changes ?
There may be relevant/material improvements to handling of this in
2.0;
ok, but I cannot use it (postgresql 8.2)
I don't think there's anything to be done in terms of
configuration.
For your information I'm using version 1.2.10.
--
Cyril SCETBON
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
