From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: System load consideration before spawning parallel workers |
Date: | 2016-08-04 23:46:26 |
Message-ID: | 4aaf837e-015c-eb56-a1ff-72ec6636baf4@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/1/16 1:08 AM, Haribabu Kommi wrote:
> There are some utilities and functions that are available to calculate the
> current system load, based on the available resources and system load,
> the module can allow the number of parallel workers that can start. In my
> observation, adding this calculation will add some overhead for simple
> queries. Because of this reason, i feel this can be hook function, only for
> the users who want it, can be loaded.
I think we need to provide more tools to allow users to control system
behavior on a more dynamic basis. How many workers to launch is a good
example. There's more reasons than just CPU that parallel workers can
help (IO being an obvious one, but possible other things like GPU).
Another example is allowing users to alter the selection process used by
autovac workers.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-08-05 00:28:26 | Re: Fwd: [BUGS] BUG #14247: COMMENT is restored on wrong database |
Previous Message | Bruce Momjian | 2016-08-04 23:31:28 | Re: Heap WARM Tuples - Design Draft |