From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Ashutosh Sharma' <ashu(dot)coek88(at)gmail(dot)com>, 'Thomas Munro' <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Supporting huge pages on Windows |
Date: | 2017-03-09 01:36:35 |
Message-ID: | 0A3221C70F24FB45833433255569204D1F6AF69B@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Ashutosh Sharma
> To start with, I ran the regression test-suite and didn't find any failures.
> But, then I am not sure if huge_pages are getting used or not. However,
> upon checking the settings for huge_pages and I found it as 'on'. I am
> assuming, if huge pages is not being used due to shortage of large pages,
> it should have fallen back to non-huge pages.
You are right, the server falls back to non-huge pages when the large pages run short.
> I also ran the pgbench tests on read-only workload and here are the results
> I got.
>
> pgbench -c 4 -j 4 - T 600 bench
>
> huge_pages=on, TPS = 21120.768085
> huge_pages=off, TPS = 20606.288995
Thanks. It's about 2% improvement, which is the same as what I got.
From: Thomas Munro [mailto:thomas(dot)munro(at)enterprisedb(dot)com]
> The line beginning 'Huge pages are known as...' has been accidentally
> duplicated.
Oops, how careless I was. Fixed. As Ashutosh referred, I added a very simple suggestion to use Windows Group Policy tool.
Regards
Takayuki Tsunakawa
Attachment | Content-Type | Size |
---|---|---|
win_large_pages_v9.patch | application/octet-stream | 8.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-03-09 01:45:33 | Re: Cost model for parallel CREATE INDEX |
Previous Message | Robert Haas | 2017-03-09 01:33:09 | Re: Cost model for parallel CREATE INDEX |