Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance

From: Jim Nasby <jim(at)nasby(dot)net>
To: Jan Kara <jack(at)suse(dot)cz>, Mel Gorman <mgorman(at)suse(dot)de>
Cc: Claudio Freire <klaussfreire(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Joshua Drake <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "lsf-pc(at)lists(dot)linux-foundation(dot)org" <lsf-pc(at)lists(dot)linux-foundation(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance
Date: 2014-01-14 00:55:41
Message-ID: 52D48B0D.3080907@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/13/14, 4:47 PM, Jan Kara wrote:
> Note to postgres guys: I think you should have a look at the proposed
> 'vrange' system call. The latest posting is here:
> http://www.spinics.net/lists/linux-mm/msg67328.html. It contains a rather
> detailed description of the feature. And if the feature looks good to you,
> you can add your 'me to' plus if anyone would be willing to try that out
> with postgress that would be most welcome (although I understand you might
> not want to burn your time on experimental kernel feature).

I don't think that would help us with buffers unless we switched to MMAP (which is a huge change), but this part is interesting:

"* Opportunistic freeing of memory that may be quickly reused. Minchan
has done a malloc implementation where free() marks the pages as
volatile, allowing the kernel to reclaim under pressure. This avoids the
unmapping and remapping of anonymous pages on free/malloc."

Postgres has it's own memory management on top of malloc that gives us memory contexts; some of those contexts get destroyed frequently. Allowing the kernel to reclaim that free'd memory in the background might be a performance win for us.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-01-14 00:57:04 Re: plpgsql.consistent_into
Previous Message Trond Myklebust 2014-01-14 00:48:56 Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance