From: | hvjunk <hvjunk(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: building a server |
Date: | 2017-12-03 22:17:36 |
Message-ID: | 82D17122-B2DE-4B90-8945-790EF40ED87D@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 03 Des. 2017, at 23:39 , Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> On 12/03/2017 02:15 PM, John R Pierce wrote:
>> On 12/3/2017 12:47 PM, Gmail wrote:
>>> So I revisited https://momjian.us/main/writings/pgsql/hw_selection.pdf <https://momjian.us/main/writings/pgsql/hw_selection.pdf>
>>> Near the end (page 24) I spotted:
>>> Heavy use of server-side functions might generate significant CPU load
>>> Just want to confirm that this referring to workload on the mainly-single-threaded server not an advocacy for more cores.
>>>
>> well, if you have significant concurrency with high CPU usage, you want both more AND faster cores
>>
>> john r pierce, recycling bits in santa cruz
>>
> Granted! I suppose I'm looking for confirmation/correction on believing that for the server to make use of multiple cores is more dependent on the nature of the queries handled. Concurrency should not be a huge problem for this project, though I've put pieces in place to mitigate that issue.
I would not say that much on the “nature of the queries”, but more on the “number of concurrent sessions doing queries”. Granted that with the later postgresql versions, given you’ve set the needed to enable parallel queries and you have “big-enough-tables” some selects does make use of multiple cores.
As they always say: YMMV
From | Date | Subject | |
---|---|---|---|
Next Message | Yuri Budilov | 2017-12-03 23:18:50 | JSON out of memory error on PostgreSQL 9.6.x |
Previous Message | John R Pierce | 2017-12-03 21:45:48 | Re: building a server |