| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | sthomas(at)optionshouse(dot)com |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Tons of free RAM. Can't make it go away. |
| Date: | 2012-10-22 18:14:03 |
| Message-ID: | CAGTBQpZ-+zxkZfkyKr7ZZdfGC6D2FunrZBx3yo4kOwAiD1fzdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Oct 22, 2012 at 3:01 PM, Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
>
>> Did you check the kernel's zone_reclaim_mode ?
>
>
> It's currently set to 0, which as I'm led to believe, is the setting I want
> there.
Yep
> But here's something interesting:
>
> numactl --hardware
>
> available: 2 nodes (0-1)
> node 0 cpus: 0 2 4 6 8 10 12 14 16 18 20 22
> node 0 size: 36853 MB
> node 0 free: 13816 MB
> node 1 cpus: 1 3 5 7 9 11 13 15 17 19 21 23
> node 1 size: 36863 MB
> node 1 free: 751 MB
> node distances:
> node 0 1
> 0: 10 20
> 1: 20 10
>
>
> Looks like CPU 0 is hoarding memory. :(
You may want to try setting the numa policy before launching postgres:
numactl --interleave=all pg_ctl start
or
numactl --preferred=+0 pg_ctl start
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Franklin, Dan (FEN) | 2012-10-22 18:20:09 | Re: Tons of free RAM. Can't make it go away. |
| Previous Message | Shaun Thomas | 2012-10-22 18:01:28 | Re: Tons of free RAM. Can't make it go away. |