From: <sarbx-cygwin6344@mailblocks.com>
To: cygwin@cygwin.com
Subject: Re: cygserver - Postgres Multiple connection Load Testing - Inifinte Loop
Date: Tue, 03 Aug 2004 03:33:00 -0000 [thread overview]
Message-ID: <20040803033300.hiCWJdY3jJfyFlSnkMFLEn14TJewlwURSLxSvaqQBpg@z> (raw)
>On Jul 30 14:32, sarbx-cygwin6344@mailblocks.com wrote:
>> >On Jul 28 20:19, sarbx-cygwin6344@mailblocks.com wrote:
>> >>$ postgres --version
>> >>postgres (PostgreSQL) 7.4.3
>> >>
>> >>$ uname -a
>> >>CYGWIN_NT-5.0 sbellan-nb 1.5.10(0.116/4/2) 2004-05-25 22:07 i686
>> >>unknown unknown
>> >>Cygwin
>> >>
>> >>While doing Load testing using DOTS, after 5 to 6 connections the
>> >>machine starts to slow down and
>> >>cygserver seems to hog most of the CPU. After running the cygserve
>> in
>> >>debug mode , I see the following
>> >>in the log file repeating infinitely.
>> >>[...]
>> >
>> >Just to be sure, are you talking about 5 or 6 *concurrent*
connections?
>> >That might be important. I'm not exactly sure so far but there
might
>> >be a race condition in my mutex code.
>> >
>> >Corinna
>>
>> Yes, I'm talking about 5 or 6 *concurrent* connections.
>
>Ok, that's what I'd suspected. I have patched Cygserver and I'd like
to
>get some feedback on whether this solves the problem or not. Would you
>please try the latest developer snapshot from
http://cygwin.com/snapshots/
>and report if that version of Cygserver still eats up CPU time under
the
>above circumstances?
>
>
>Corinna
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.
Let me know a alternate address where I can send you the log file.
----------------------------------------------
Mailblocks - A Better Way to Do Email
http://about.mailblocks.com/info
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2004-08-03 3:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 3:33 sarbx-cygwin6344 [this message]
[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)
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
[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=20040803033300.hiCWJdY3jJfyFlSnkMFLEn14TJewlwURSLxSvaqQBpg@z \
--to=sarbx-cygwin6344@mailblocks.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).