delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2017/03/21/03:29:32

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:subject:to:references:from:message-id:date
:mime-version:in-reply-to:content-type
:content-transfer-encoding; q=dns; s=default; b=GuatKdFH8vN2qX9G
oulH2LUdE7K0HGK5wYuHo5CkfubyCKUS4A6+mI24umqskVE9SMEnKIw2cgL7mMyW
n5qp8HdOLDjBcyb8O6fYeTviTy+qo7tjb1OckQOZ5z/PCHPv5slNxKGbqoo5G0To
42L41LxgI5CBnbjvqcPFURWf5VM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:subject:to:references:from:message-id:date
:mime-version:in-reply-to:content-type
:content-transfer-encoding; s=default; bh=WH5JF+KoPRq90B/r8PibTn
VLTQs=; b=Jha/O6ulKgfVh13Z5lxlWRJZ7nIBxmvtM5IDzcsryGvuhYGjGb58hG
RzCjhh9cKSwTOYd8c8cZIaK7mLmBFylGnrn7xSBj3MKbZYxWz0Hswf8rJ0mrzios
ysEyKHQ+6+exOz+ugsZK7uuXnUHyMVjJ50LQ4LX2pE4+sbEFds0rc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=million, Misch, misch, Noah
X-HELO: mail-wr0-f169.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=RZE7CJHwgZfLkC1HY0f9e3lEjBWxG7buemtXnRQP61M=; b=IAN3KtU4ymTgvCCeh+p8ZAX46OCDfAOdDcjxzeSk4Thzg5zgXmjF9Vo4NiHQTpavcQ +jzTHiC6TonCLKpXPFrGol/cZUaKKoXNtSyOXx9FLauKH08/siojHK/rVeceqIOVS0Ga py7Jz7p7QMN0b+31/1H/fn2RFNcX3cEiItF1S8vu/JJ472CcfxJG2s6jwwJjbhEAhv8Z 59VqQ/J5q3q3iBvAIEpsNjpcDx4zyshNGB3ukFEk6L1iXu1CwHboekqOlTCrPGrhmOXE f7PCGgbZojJXrmGdDOue4lT4M7RaKbhO6Tb+28vtHII7JHHddhSfV63jypoS4dNxAqj+ z8XA==
X-Gm-Message-State: AFeK/H2cDNCMD/VipqelOdeLRORNHcINQVNGSWOSiZIVHxjxvA65hOnIVLrwpsA2LmrXqA==
X-Received: by 10.223.134.157 with SMTP id 29mr28340011wrx.33.1490081345755; Tue, 21 Mar 2017 00:29:05 -0700 (PDT)
Subject: Re: cygserver - Postgres Multiple connection Load Testing - Inifinte Loop
To: cygwin AT cygwin DOT com
References: <200408030333 DOT i733XEXn023894 AT mx3 DOT redhat DOT com> <20040803100612 DOT GP31522 AT cygbert DOT vinschen DOT de> <20170321025614 DOT GA2100214 AT tornado DOT leadboat DOT com>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <8fd6c531-0fdc-3c81-c932-e601cddec714@gmail.com>
Date: Tue, 21 Mar 2017 08:29:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170321025614.GA2100214@tornado.leadboat.com>
X-IsSubscribed: yes

On 21/03/2017 03:56, Noah Misch wrote:
> On Tue, Aug 03, 2004 at 12:06:12PM +0200, Corinna Vinschen wrote:
>> On Aug  2 20:33, sarbx-cygwin6344 AT mailblocks DOT com wrote:
>>> This time around, cygserver does not eat CPU. But after 5 to 6
>>> concurrent
>>> connections nothing seem to work, looks kind of hung. There is no
>>> activity in the Postgres
>>> log file. Opening a new database connection also hangs. There is no
>>> activity on the machine.
>
>> Any chance to create a simple testcase which uncovers that behaviour
>> without involving a whole database system?
>
> Attached test program reproduces it on Cygwin 2.7.0, Cygwin 1.7.5, and a few
> intermediate versions.  The program creates sixteen processes that each
> perform a tight loop over the following:

same on x86_64 2.8.0-0.1

>
> - select one of four semaphores
> - reduce semaphore's value from 1 to 0 ("lock" it)
> - raise semaphore's value from 0 to 1 ("unlock" it)
>
> On GNU/Linux, AIX, and Solaris, the processes keep busy and finish one million
> lock/unlock cycles apiece in a few minutes.  On Cygwin, they hang within a few
> seconds and under one hundred cycles apiece.  At that point, cygserver is
> unresponsive to other clients; for example, "strace /bin/true", opening a new
> Cygwin terminal, "cat /proc/sysvipc/sem" and "cygserver -S" all hang.  In most
> tests, cygserver was not consuming CPU while unresponsive.

confirmed

> Thanks,
> nm
>

Regards
Marco

--
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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019