Looks like Postgres will never "use" (visually) more than shared_buffers
size of memory.
Change it to 48GB, and in your "top" output you will see how memory
usage bumped up to this new limit.
But it's just a "visual" change, I doubt you'll get any benefits from it.
On 03/24/17 02:58,
> What’s wrong with this? There isn’t something wrong in RAM usage?
Nope, nothing wrong with RAM usage at all from what you've presented
here. Please consider the cut-and-paste you included a bit closer. All
of your active threads are utilizing 100% CPU, and are therefore
CPU-bound. If there were
On 24/03/17 10:58, Pietro Pugni wrote:
Hi there,
I’m running PostgreSQL 9.6.2 on Ubuntu 16.04.2 TLS (kernel
4.4.0-66-generic). Hardware is:
- 2 x Intel Xeon E5-2690
- 96GB RAM
- Software mdadm RAID10 (6 x SSDs)
Postgres is used in a sort of DWH application, so all the resources
are
On Fri, Mar 24, 2017 at 3:58 AM, Pietro Pugni wrote:
> Hi there,
> I’m running PostgreSQL 9.6.2 on Ubuntu 16.04.2 TLS (kernel
> 4.4.0-66-generic). Hardware is:
> - 2 x Intel Xeon E5-2690
> - 96GB RAM
> - Software mdadm RAID10 (6 x SSDs)
>
> Postgres is used in a sort of
On Tue, Mar 21, 2017 at 4:24 PM, James Parks wrote:
> What can I do to keep running long maintenance operations on large
> tables (SELECTing significant fractions of B, DELETEing significant
> fractions of B, running VACUUM FULL on B) without denying other
> Postgresql
As I read this, you have 24G of hugepages, and hugepages enabled for
postgres. Can postgres use both standard pages and hugepages at the same
time? Seems unlikely to me.
On Fri, Mar 24, 2017 at 4:58 AM, Pietro Pugni
wrote:
> Hi there,
> I’m running PostgreSQL 9.6.2 on
Hi there,
I’m running PostgreSQL 9.6.2 on Ubuntu 16.04.2 TLS (kernel 4.4.0-66-generic).
Hardware is:
- 2 x Intel Xeon E5-2690
- 96GB RAM
- Software mdadm RAID10 (6 x SSDs)
Postgres is used in a sort of DWH application, so all the resources are
assigned to it and the aim is to maximize the