| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Claudio Freire <klaussfreire(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NUMA packaging and patch |
| Date: | 2014-06-26 16:14:39 |
| Message-ID: | 1403799279.67192.YahooMailNeo@web122302.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
> Sadly, it excludes the OS cache explicitly (when it mentions libc.so),
> which is one of the hottest sources of memory bandwidth consumption in
> a database.
Agreed. On the bright side, the packagers and/or sysadmins can fix this
without any changes to the PostgreSQL code, by creating a custom cpuset
and using it during launch of the postmaster. I went through that
exercise in my original email. This patch complements that by
preventing one CPU from managing all of PostgreSQL shared memory, and
thus becoming a bottleneck.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-06-26 17:04:46 | Re: RLS Design |
| Previous Message | Andrew Dunstan | 2014-06-26 15:38:14 | Re: What's the point of json_extract_path_op etc? |