Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Cygwin signal bandwidth Date: Sun, 9 Feb 2003 13:36:16 -0500 Message-ID: <83040F98B407E6428FEC18AC720F5D732DB7C2@exchange.tropicnetworks.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rolf Campbell" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h19IaXq29115 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 receive 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/