| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "basti *EXTERN*" <mailinglist(at)unix-solution(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Linux OOM-Killer |
| Date: | 2014-03-17 11:55:47 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17CE578E@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
basti wrote:
>>> Since a few days we had problems with the Linux OOM-Killer.
>>> Some simple query that normally take around 6-7 minutes now takes 5 hours.
>>> We did not change any configuration values the last days.
>>>
>>> First of all I have set
>>>
>>> vm.overcommit_memory=2
>>> vm.overcommit_ratio=80
> Swap is disabled.
> free -m
> total used free shared buffers cached
> Mem: 32215 16163 16051 0 40 14842
> -/+ buffers/cache: 1281 30934
> Swap: 0 0 0
That together means that you cannot use more than 80% of your
RAM. Are you hitting that limit?
See the description of overcommit_ratio in
https://www.kernel.org/doc/Documentation/sysctl/vm.txt
I would definitely add some swap.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | José Pedro Santos | 2014-03-17 12:50:20 | Dump Database |
| Previous Message | Karsten Hilbert | 2014-03-17 11:36:29 | Re: Linux OOM-Killer |