| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tory M Blue <tmblue(at)gmail(dot)com> |
| Cc: | David Rees <drees76(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: oom_killer |
| Date: | 2011-04-23 19:24:28 |
| Message-ID: | A245910A-7980-42D1-B2B5-EEEDCF173CAA@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Apr 22, 2011, at 2:22 PM, Tory M Blue <tmblue(at)gmail(dot)com> wrote:
> Thanks David and I have and in fact I do see spikes that would cause
> my system to run out of memory, but one thing I'm struggling with is
> my system always runs at the limit. It's the nature of linux to take
> all the memory and manage it.
One thing to watch is the size of the filesystem cache. Generally as the system comes under memory pressure you will see the cache shrink. Not sure what is happening on your system, but typically when it gets down to some minimal size, that's when the swapping starts.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-04-23 19:34:11 | Re: big distinct clause vs. group by |
| Previous Message | Robert Haas | 2011-04-23 16:11:38 | Re: Shouldn't we have a way to avoid "risky" plans? |