public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.santos@pobox.com>
To: cygwin@cygwin.com
Subject: Re: long I/O delays when strace is running
Date: Fri, 21 Apr 2017 07:57:00 -0000	[thread overview]
Message-ID: <46e39bce-9782-5c74-c196-35ee97ebbc64@pobox.com> (raw)
In-Reply-To: <91DCAC3CB99C724EB365BB64677FBE7B16EBBD@MX204CL04.corp.emc.com>

On 04/20/2017 08:43 AM, Gluszczak, Glenn wrote:
> I haven't run Cygwin Expect for about 6 moths on Windows but it was behaving fine last time I did.
> One thing I am aware of is you can't interrupt sleep in TCL.  The sleep must
> complete until the Control C is processed (regardless of whether you redirected signals
> to your own routines).  Otherwise signals seemed to be processed immediately.

Please note that my simplified test case isn't using expect, but the 
standard /usr/bin/sleep.exe -- this is just to have strace run and trace 
for a longer amount of time in order to expose the problem. (it did get 
broken into a new line though, so add a backslash:

> for ((i = 0; i < 64; ++i)); do strace --output=/tmp/sleep.$$.log \
> --trace-children --mask=startup sleep 64; done

> Perhaps some other service is interfering.  You may want to disable other services.
>
> Glenn

I usually disable most services, I can probably disable a few more, but 
I would like if somebody can run the above test case in one terminal 
windows and in the other terminal window do a simple ps -ef and let me 
know if ps responds immediately or has a delay.  I am using Windows 7, 
so it could be isolated to that windows version as well.  When I do 
this, ps has a 3 second delay while in 
fhandler_base_overlapped::wait_overlapped, but I've seen this delay in 
other processes while calling something like "open_shared."

Anyway, I'm going to try to find another simple test case that causes 
more of a drastic delay.

Daniel

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

  reply	other threads:[~2017-04-21  2:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 18:13 Daniel Santos
2017-04-21  0:11 ` Gluszczak, Glenn
2017-04-21  7:57   ` Daniel Santos [this message]
2017-04-21  9:38     ` Daniel Santos
2017-04-21 11:06       ` Daniel Santos
2017-04-21 12:08         ` Mark Geisert
2017-04-21 18:23           ` Daniel Santos
2017-04-22 15:24             ` Mark Geisert
2017-04-23 12:58               ` Daniel Santos
2017-04-23 18:15                 ` Mark Geisert
2017-04-24  8:23                   ` Daniel Santos
2017-04-24  9:24                   ` Daniel Santos
2017-04-24  9:34                     ` Mark Geisert
2017-04-24 15:00                       ` Daniel Santos
2017-04-24 19:30                       ` Daniel Santos

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=46e39bce-9782-5c74-c196-35ee97ebbc64@pobox.com \
    --to=daniel.santos@pobox.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).