Re: Performance monitor signal handler - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Performance monitor signal handler
Date
Msg-id 1325.984847702@sss.pgh.pa.us
Whole thread Raw
In response to Re: Performance monitor signal handler  (Samuel Sieb <samuel@sieb.net>)
Responses Re: Performance monitor signal handler  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Performance monitor signal handler  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Samuel Sieb <samuel@sieb.net> writes:
> Just as another suggestion, what about sending the data to a different
> computer, so instead of tying up the database server with processing the
> statistics, you have another computer that has some free time to do the
> processing.

> Some drawbacks are that you can't automatically start/restart it from the
> postmaster and it will put a little more load on the network,

... and a lot more load on the CPU.  Same-machine "network" connections
are much cheaper (on most kernels, anyway) than real network
connections.

I think all of this discussion is vast overkill.  No one has yet
demonstrated that it's not sufficient to have *one* collector process
and a lossy transmission method.  Let's try that first, and if it really
proves to be unworkable then we can get out the lily-gilding equipment.
But there is tons more stuff to do before we have useful stats at all,
and I don't think that this aspect is the most critical part of the
problem.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: beta6 pg_restore core dumps
Next
From: Tom Lane
Date:
Subject: Re: Stuck spins in current