From: | Michael Curry <curry(at)cs(dot)umd(dot)edu> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | perf tuning for 28 cores and 252GB RAM |
Date: | 2019-06-17 20:50:41 |
Message-ID: | CAEqv4-34dyUErMcB3mwyD6MB+ckH_HFqMQg3Hb2F81NhjP78cw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am using a Postgres instance in an HPC cluster, where they have
generously given me an entire node. This means I have 28 cores and 252GB
RAM. I have to assume that the very conservative default settings for
things like buffers and max working memory are too small here.
We have about 20 billion rows in a single large table. The database is not
intended to run an application but rather to allow a few individuals to do
data analysis, so we can guarantee the number of concurrent queries will be
small, and that nothing else will need to use the server. Creating multiple
different indices on a few subsets of the columns will be needed to support
the kinds of queries we want.
What settings should be changed to maximize performance?
--
Michael J. Curry
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Tanzer | 2019-06-17 22:03:11 | psql UPDATE field [tab] expands to DEFAULT? |
Previous Message | Leandro Guimarães | 2019-06-17 19:01:57 | Re: Copy Bulk Ignore Duplicated |