Re: pmlogger(1) task_t optimisations

[fche@xxxxxxxxxx (Frank Ch. Eigler)]

nathans wrote:

> [...]
> An ideal outcome would have been 1 task_t matching just that
> final block - one pmFetch PDU, one sample on the server side,
> one timestamp, and one result logged.

Right.  One way to do this would be to have the parser generate one
task_t per "(permission,time)" tuple rather than build duplicates
per config-language { } group.  Then as we parse metrics, they'd get
dropped into the one-or-few distinct task_t's, duplicate-eliminated
as we go, and optfetched then or once at the end.

- FChE