From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Васильев Дмитрий <d(dot)vasilyev(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: modifying WaitEventSets (was: Performance degradation in commit ac1d794) |
Date: | 2016-05-04 19:35:33 |
Message-ID: | CAHyXU0y4XQPg++nkc3siL7fPiczoKeLgU1BYamy8c7u684_91A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 4, 2016 at 2:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> Given that poll() has been introduced in SRV3 - which IIRC was below our
>> usual baseline - and windows is not an issue for latch, I think it'd
>> be ok to rely on it.
>
> I think it's entirely reasonable to say that "if you want high performance
> you should have poll(3)". Failing to build without it would be a harder
> sell, probably.
There are some decent cross platform libraries that expose high
performance polling. In particular, libev.
http://software.schmorp.de/pkg/libev.html. I would definitely look
there before contemplating direct epoll calls. (note, aside from
seeing epoll, I haven't been following this thread in detail).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-04 19:35:39 | Re: modifying WaitEventSets (was: Performance degradation in commit ac1d794) |
Previous Message | Tom Lane | 2016-05-04 19:31:35 | Re: modifying WaitEventSets (was: Performance degradation in commit ac1d794) |