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

Re: Report: Linux huge pages with Postgres

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Report: Linux huge pages with Postgres
Date: 2010-11-28 16:53:37
Message-ID: 1290963217.4634.190.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
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? 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.

-- 
 Simon Riggs           http://www.2ndQuadrant.com/books/
 PostgreSQL Development, 24x7 Support, Training and Services
 


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-11-28 17:04:43
Subject: Re: Report: Linux huge pages with Postgres
Previous:From: Tom LaneDate: 2010-11-28 16:50:21
Subject: Re: PLy_malloc and plperl mallocs

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