Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Rolf Campbell <rcampbell AT tropicnetworks DOT com>
Subject:	Cygwin signal bandwidth
Date:	Sun, 09 Feb 2003 12:07:10 -0500
Lines:	11
Message-ID:	<b261o2$lo0$1@main.gmane.org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language:	en-us, en

While working on a project, I had the need to run a function every 
millisecond.  So, my first attempt was to fork() and then loop sending a 
signal then delaying 1ms.  What I found was that a cygwin process can 
only recieve about 100 signals/sec before it uses up 100% of the 
processor (on a PIII/850MHz).

Is it reasonable for me to conclude that cygwin uses about 8,000,000 
cycles to process a single signal, or have I done something wrong?

-Rolf



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -