| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Graeme B(dot) Bell" <graeme(dot)bell(at)nibio(dot)no> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Hmmm... why does pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? |
| Date: | 2015-07-07 20:52:28 |
| Message-ID: | CAHyXU0yzuYdjugieTk3NabXHMwMwkRQ+ZX7nSDyT-h-40+i54g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jul 7, 2015 at 3:33 PM, Graeme B. Bell <graeme(dot)bell(at)nibio(dot)no> wrote:
>
> Hi Merlin,
>
> Long story short - thanks for the reply, but you're not measuring anything about the parallelism of code running in a pl/pgsql environment here. You're just measuring whether postgres can parallelise entering that environment and get back out. Don't get me wrong - it's great that this scales well because it affects situations where you have lots of calls to trivial functions.
> However it's not the problem I'm talking about. I mean 'real' pl'pgsql functions. e.g. things that you might find in postgis or similar.
Maybe so. But it will be a lot easier for me (and others on this)
list if you submit a self contained test case that runs via pgbench.
From there it's a simple matter of a perf top and other standard
locking diagnostic tests and also rules out any suspicion of 3rd party
issues. This will also get better feedback on -bugs.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig James | 2015-07-08 03:05:57 | Re: Hmmm... why does CPU-intensive pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? |
| Previous Message | Graeme B. Bell | 2015-07-07 20:33:34 | Re: Hmmm... why does pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? |