Christopher Browne <cbbrowne at ca.afilias.info> writes:
> Over lunch, Jan and I had a chat about this; it looks like we don't
> report quite comprehensive enough information in the logs to make it
> easy to interpret what parts of SYNC processing are consuming what
> time.
>
> The "straw man" idea we came up with is to do a much better breakdown
> of the time, in particlar, to record:
>
>  - time spent in pqexec() against the provider, broken down into...
>     - time spent processing what transactions are part of the SYNC group
>     - time spent processing the LOG cursor
>  - time spent in pqexec() against the subscriber (the I/U/D phase)
>  - numbers of pqexecs()
>     against provider
>     against subscriber
>  - possibly, the number of times we grab timestamps

And, let us augment this with the number of "large tuple" fetches...
That will be really cheap from gettimeofday() perspective, but gives
us a good idea of how much flow interruption takes place.
-- 
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/>