From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygserver - Postgres Multiple connection Load Testing - Inifinte Loop
Date: Sun, 07 May 2017 04:01:00 -0000 [thread overview]
Message-ID: <590E98DD.9000805@cygwin.com> (raw)
In-Reply-To: <20170507032747.GA876495@rfd.leadboat.com>
On 05/06/2017 11:27 PM, Noah Misch wrote:
> On Sat, Apr 01, 2017 at 10:36:24PM -0400, Noah Misch wrote:
>> On Tue, Mar 28, 2017 at 01:26:52AM -0400, Noah Misch wrote:
>>> On Fri, Mar 24, 2017 at 06:11:01PM +0100, Corinna Vinschen wrote:
>>>> I pushed a patchset now, and uploaded new developer snapshots for
>>>> testing to https://cygwin.com/snapshots/
>>>
>>>> Please give it a try
>>
>>> I call the cygwin-20170324 freezes "limited" because the symptoms differ from
>>> the classic freeze I described upthread. "strace /bin/true" and "cat
>>> /proc/sysvipc/sem" do not hang, but every PostgreSQL backend process is stuck
>>> waiting on a synchronization primitive.
>>>
>>> I can distill another self-contained test case for the limited freeze seen in
>>> cygwin-20170324, but that make take awhile. I'm sending this early report so
>>> you're aware of the possible regression in cygwin-20170324.
>>
>> I'm attaching a new test program that demonstrates the regression. My previous
>> test program created sixteen processes that each picked a random semaphore to
>> lock. Now, each process picks two semaphores and locks them in order. This
>> proceeds smoothly on GNU/Linux and on cygwin-20170321.tar.xz "cygserver -r 40".
>> It freezes within one second on cygwin-20170324.tar.xz "cygserver -r 40".
>
> I suggest reverting the cygwin-20170324 cygserver changes for now. Older
> versions can be configured to have reliable sysv semaphores, but I think no
> settings render sysv semaphores reliable in Cygwin 2.8.0. What do you think?
Just FYI, Corinna is away for a bit (in European time, "a bit" = until
June ;-) ) so don't be surprised if her response is delayed.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-05-07 3:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408030333.i733XEXn023894@mx3.redhat.com>
2004-08-03 10:06 ` Corinna Vinschen
2004-08-03 20:45 ` Saravanan Bellan
2004-08-03 20:54 ` Christopher Faylor
2004-08-03 21:10 ` Saravanan Bellan
2017-03-21 2:56 ` Noah Misch
2017-03-21 7:29 ` Marco Atzeri
2017-03-24 17:52 ` Corinna Vinschen
2017-03-25 10:55 ` Marco Atzeri
2017-03-25 12:02 ` Corinna Vinschen
2017-03-25 12:31 ` Marco Atzeri
2017-03-28 5:48 ` Noah Misch
2017-04-02 2:36 ` Noah Misch
2017-05-07 3:35 ` Noah Misch
2017-05-07 4:01 ` Larry Hall (Cygwin) [this message]
2017-06-14 23:32 ` Marco Atzeri
2017-06-20 11:11 ` Corinna Vinschen
2017-06-20 17:29 ` Marco Atzeri
2017-06-21 7:58 ` Corinna Vinschen
2004-08-03 3:33 sarbx-cygwin6344
[not found] <200407302132.i6ULWwXn016838@mx3.redhat.com>
2004-08-02 9:45 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 22:09 sarbx-cygwin6344
[not found] <200407290319.i6T3JCXn018245@mx3.redhat.com>
2004-07-30 13:43 ` Corinna Vinschen
2004-07-29 10:35 sarbx-cygwin6344
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=590E98DD.9000805@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).