Skip site navigation (1) Skip section navigation (2)

Re: Report: Linux huge pages with Postgres

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Report: Linux huge pages with Postgres
Date: 2010-11-28 17:04:43
Message-ID: 22435.1290963883@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On Sat, 2010-11-27 at 14:27 -0500, Tom Lane wrote:
>> This is discouraging; it certainly doesn't make me want to expend the
>> effort to develop a production patch.

> Perhaps.

> Why do this only for shared memory?

There's no exposed API for causing a process's regular memory to become
hugepages.

> Surely the majority of memory
> accesses are to private memory, so being able to allocate private memory
> in a single huge page would be better for avoiding TLB cache misses.

It's not really about the number of memory accesses, it's about the
number of TLB entries needed.  Private memory is generally a lot smaller
than shared, in a tuned PG installation.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2010-11-28 19:15:01
Subject: Re: Report: Linux huge pages with Postgres
Previous:From: Simon RiggsDate: 2010-11-28 16:53:37
Subject: Re: Report: Linux huge pages with Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group