Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B393608.B5FF9562@nc.rr.com>
Date: Tue, 26 Jun 2001 21:25:28 -0400
From: Greg Smith <gsmith AT nc DOT rr DOT com>
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: pthreads works, sorta
References: <3B37D1A6 DOT 39A2685 AT nc DOT rr DOT com> <03c701c0fdd7$82ddbde0$0200a8c0 AT lifelesswks> <3B37F19F DOT C9BCDA23 AT nc DOT rr DOT com> <003d01c0fe1c$1f7e3c80$0200a8c0 AT lifelesswks> <3B38CED1 DOT 45B44DBD AT trex DOT rtpnc DOT epa DOT gov> <3B393395 DOT DF14BC5C AT nc DOT rr DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

More experimenting with my home computer, dual pIII 850:

1. 117  157 328
2. 822 1527 ---
3. 194  240 453
4. 169  181 516

The entries in the array represent the number of seconds it
took to get to a certain milestone in the application.  The
columns, 1 thru 3, are the milestones.  The rows are defined as:

1. linux (however, linux had an advantage, since all the data is
   on the hard drive, and on the windows side some of the data
   had to be contained on cdrom).
2. cygwin current, with the condtimedwait patch
3. cygwin 1.3.2, but with the Pthread-win32 implementation
4. cygwin current, plus using the verifiable_object_isvalid2()
   routine, for the lock/unlock, signal, wait/timedwait calls
   (which doesn't call VirtualQuery()).

There is an additional error in cygwin current, I think related
to pthread_kill, that occurs between milestone 2 and 3, that
possibly skewed the results for row 4.  Milestone 3 is never
reached for row 2 because all processing becomes dedicated to
pthreads overhead and no useful work gets done (ie thrashing).

I think this shows that VirtualQuery *is* a hog.
These results were obtained on Windows2000 sp1 and my previous
results were on NT4 sp6 (on a pIII 650).

Thanks, Greg

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