| From: | Joachim Wieland <joe(at)mcknight(dot)de> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Chernow <ac(at)esilo(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrew Chernow <andrew(at)esilo(dot)com> |
| Subject: | Re: Listen / Notify rewrite |
| Date: | 2009-11-16 21:41:51 |
| Message-ID: | dc7b844e0911161341q44f3fac2id9d86187f0192114@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 14, 2009 at 11:06 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> The old method (measured on a 4 core high performance server) has
> severe scaling issues due to table bloat (we knew that):
> ./pgbench -c 10 -t 1000 -n -b listen.sql -f notify.sql
> run #1 tps = 1364.948079 (including connections establishing)
> new method on my dual core workstation (max payload 128):
> ./pgbench -c 10 -t 10000 -n -b listen.sql -f notify.sql -hlocalhost postgres
> tps = 16343.012373 (including connections establishing)
That looks fine and is similar to my tests where I also see a
performance increase of about 10x, and unlike pg_listener it is
constant.
> getting sporadic 'LOG: could not send data to client: Broken pipe'
> throughout the test.
This looks like the server is trying to send a notification down to
the client but the client has already terminated the connection...
Joachim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-11-16 21:46:09 | Re: Listen / Notify rewrite |
| Previous Message | Tom Lane | 2009-11-16 21:39:15 | Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" |