Re: So, can we stop supporting Windows native now? - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: So, can we stop supporting Windows native now?
Date
Msg-id CAEepm=075-bgHi_VDt4SCAmt+o_+1XaRap2zh7XwfZvT294oHA@mail.gmail.com
Whole thread Raw
In response to Re: So, can we stop supporting Windows native now?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Apr 1, 2016 at 11:44 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Thomas Munro wrote:
>> On Fri, Apr 1, 2016 at 2:53 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
>> > It would also be nice to find out why we can't usefully scale shared buffers
>> > higher like we can on *nix.
>>
>> Has anyone ever looked into whether asking for SEC_LARGE_PAGES would
>> help with that?
>
> The huge_pages feature is fairly new, and as I recall the intention is
> that other operating systems will be supported as we get patches for it.
> Feel free to submit something.

I don't have a Windows development stack or any plans to get one but I
did make some notes and write some blind code for this a while back
when I was studying the shmem code.  Here it is, in the hope that it
might be a useful starting point for someone else...  I suppose the
first step is to find a benchmark that improves as you increase
shared_buffers on Windows and Linux but plateaus at a much lower
setting on Windows, and then get a patch like this working and see if
huge_pages = on changes anything...

--
Thomas Munro
http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Incorrect format in error message
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Enable logical slots to follow timeline switches