From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgbench stopped supporting large number of client connections on Windows |
Date: | 2020-11-08 08:44:56 |
Message-ID: | alpine.DEB.2.22.394.2011080930270.1605435@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Tom,
>> Use ppoll, and start more threads but not too many?
>
> Does ppoll exist on Windows?
Some g*gling suggest that the answer is no.
> There was a prior thread on this topic, which seems to have drifted off
> into the sunset:
Indeed. I may have contributed to this dwindling by not adding a CF entry
for this thread, so that there was no reminder anywhere.
It seems that there is no simple good solution around windows wait event
implementations:
- timeout seems to be milliseconds on all things I saw
- 64 is an intrinsic limit, probably because of the underlying n² implementations
Maybe we could provide a specific windows implementation limited to 64 fd
(which is not a bad thing bench-wise) but with a rounded-down timeout, so
that it could end-up on an activate spinning wait in some cases, which is
probably not a bug issue, all things considered.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Fan | 2020-11-08 09:34:34 | Re: Allow "snapshot too old" error, to prevent bloat |
Previous Message | Dilip Kumar | 2020-11-08 06:24:04 | Re: Re: parallel distinct union and aggregate support patch |