| From: | Andrzej Krawiec <a(dot)krawiec(at)focustelecom(dot)pl> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6650: CPU system time utilization rising few times a day |
| Date: | 2012-07-02 06:40:47 |
| Message-ID: | CAAy64Hg-+4oOJorXPOFvJ=xQnQq8zwH2OoBakKiLX0h5NCtOtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ok, we are 99% sure as for what is the reason for this situation. Let's say
we have a 1 GB of free memory. Any process (especially postgres, as it is
dedicated server) wants to allocate little more. Kernel has to look through
cached memory to determine which cache pages can be dropped and allocated
as user memory. If the server is idle (almost no queries) allocating huge
amounts of memory is almost invisible, but under production load (about
100-200 transactions per second) system halts for a while, to drop some of
cache pages.
We consider setting kernel value extra_free_kbytes to some reasonably high
value to check if it helps keeping free memory at certain level.
It seems that it's not a PostgreSQL bug.
Can anyone try to confirm this?
--
Regards
Andrzej Krawiec
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-07-02 10:46:31 | Re: BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table |
| Previous Message | Greg Sabino Mullane | 2012-07-02 02:59:51 | Re: BUG #6707: ERROR: could not open relation with OID |