From: | Venkat Balaji <venkat(dot)balaji(at)verse(dot)in> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | MirrorX <mirrorx(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Re: How to track number of connections and hosts to Postgres cluster |
Date: | 2011-09-02 05:46:16 |
Message-ID: | CAFrxt0jkFwN8VRONncj=90io9diwnF=_Z1R95y-XQSCJYM3uCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Scott,
Log generation rate -
500MB size of log file is generated within minimum 3 mins to maximum of 20
mins depending on the database behavior.
I did not understand the "fsync" stuff you mentioned. Please help me know
how would fsync is related to log generation or logging host IPs in the log
file ?
Thanks
Venkat
On Tue, Aug 30, 2011 at 12:09 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Mon, Aug 29, 2011 at 11:55 PM, Venkat Balaji <venkat(dot)balaji(at)verse(dot)in>
> wrote:
> > If i notice high IO's and huge log generation, then i think Greg
> Spileburg
> > has suggested a good idea of using tcpdump on a different server. I would
> > use this utility and see how it works (never used it before). Greg
> > Spileburg, please help me with any sources of documents you have to use
> > "tcpdump".
>
> There's also a lot to be said for dumping to a dedicated local drive
> with fsync turned off. They're logs so you can chance losing them by
> putting them on a cheap fast 7200 rpm SATA drive. If your logs take
> up more than a few megs a second then they are coming out really fast.
> Do you know what your log generation rate in bytes/second is?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2011-09-02 06:42:29 | Re: Re: How to track number of connections and hosts to Postgres cluster |
Previous Message | Scott Marlowe | 2011-09-02 04:58:10 | Re: Summaries on SSD usage? |