DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=tJP8H61SCCcQGjlBI8aUJdvtEF3g
	DbgU3mFRydAnqvtqIdr2QIonUGQ913r0MNy54kxy6zDI2Uy8tqywiJa0SOinb20u
	rfudxj4RZbKUX6ZbPkp/OvljFQkVIDpLDAR/vYOZ1bMjECN3KMxja9vSzFMnQDdp
	n+ybIl3jtix4pFo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: [ANNOUNCEMENT] Updated: setup.exe (Release 2.871)
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <20150531102453.GA4323@calimero.vinschen.de>
Date: Mon, 1 Jun 2015 14:05:08 -0600
Message-Id: <3C15F869-E2D8-4DB6-912A-C325576D928B@etr-usa.com>
References: <announce.20150529135159.GA25145@calimero.vinschen.de> <CAAXzdLW4x8b9ffRR4t-0KtUq9cugBQrpu8zXF57z4MR=SGSibA@mail.gmail.com> <20150531102453.GA4323@calimero.vinschen.de>
To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On May 31, 2015, at 4:24 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> 
> On May 29 17:49, Steven Penny wrote:
>> On Fri, May 29, 2015 at 8:51 AM, Corinna Vinschen wrote:
>>> - Improved performance in terms of SHA512 checksum computation.
>> 
>> Thanks for this, but how was it done?
> 
> It was embarrassingly simple:

That reminds me of a case I ran into a few months ago.

I have some UDP stream reception code that works perfectly on Linux.  Someone wanted it on Windows, too, so I ported it in an afternoon, a relatively easy task since Winsock is mostly a superset of BSD sockets, and there wasn’t much to the app besides Standard C++ and sockets code.

It worked fine on my machine, so I shipped it off, confident that it would work just as well as the Linux version.

Then I start getting field reports about dropped packets whenever the machine wasn’t perfectly idle while running the app.

This is not a high data rate application.  With the 8 kiB buffers I was using — a perfectly sensible size for UDP — it would take about 3 ms to overflow a buffer.  That’s approximately forever in CPU time, so I felt it was more than adequate, even considering multitasking overheads.

In the end, I had to increase the UDP stack buffers for the Windows port to 64 kiB to get it to work reliably on Windows, which effectively increased the buffer time to ~23 ms.

That means the time-slice delay was somewhere between 3 and 22 ms!  That’s on the scale of HDD head seek times, one of the slowest things a computer does!
--
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