From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | Misa Simic <misa(dot)simic(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Slow concurrent processing |
Date: | 2013-03-12 14:20:18 |
Message-ID: | 513F39A2.7020902@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 03/11/2013 08:55 PM, Misa Simic wrote:
> Hi all,
>
> We have one table with list of "records for processing"...
>
> We loop trough that table and call one long runing function:
>
> do_the_math_for_record(record_id)...<snip>...
>
> but - if replace do_the_math_and_save_results with pg_sleep(1); To
> simulate long running function so processing each row - last 1 sec...
>
> Sequential processing last as expected 300 seconds!
>
> Concurrent processing last faster with higher number of
> concurrent connections - about 30 seconds with 30 connections! (much
> faster - and expected...)
>
> however, if we return our: do_the_math_and_save_results - we can't get
> better results in concurrent processing...
Sleep will not have any significant impact on CPU, memory or disk use
and thus is not a simulation of actual processing.
All you have really shown us so far is a black box. Please provide an
overview of your schemas and the type of processing you are attempting
on them.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Misa Simic | 2013-03-12 15:06:46 | Re: Slow concurrent processing |
Previous Message | Misa Simic | 2013-03-12 14:13:06 | Re: Slow concurrent processing |