Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of Farid_Zaripov@epam.com
 designates 217.21.63.3 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: atomic tests timing out on Windows
Date: Wed, 25 Jul 2007 22:39:10 +0300
Message-ID: <7BDB2168BEAEF14C98F1901FD2DE6438BB0751@epmsa009.minsk.epam.com>
Thread-Topic: Re: atomic tests timing out on Windows
Thread-Index: AcfO83i07n99AYjZTA6mIgyXHj9rYw==
From: "Farid Zaripov" <Farid_Zaripov@epam.com>
To: <stdcxx-dev@incubator.apache.org>

> Looks like the two atomic tests, atomic_add.exe and atomic_xchg.exe,
> are timing out in some (optimized) MSVC builds on Windows.

> First, the timeout seems to be set to 180 seconds on Windows but 300
> seconds on all other platforms. I think we should increase it on
> Windows to make it consistent. How do we go about adjusting the
> timeout?

> Second, I'm concerned that the atomic tests are timing out at all
> because when they run to completion they only take about 15 to 20
> seconds (depending on the hardware). Farid, have you seen this in
> your manual builds? (The test are important because they exercise
> functionality that string depends on for thread safety).

  That tests works fine, but slow. This is because of using critical
section
for synchronization for all types except signed/unsigned int and long
for
which are used InterlockedXXX functions.

  For example on my computer the one execution of the run_test<> takes
about 25 seconds when used critical section and only 3.5 seconds when
used InterlockedXXX functions. The full test takes 445 seconds. And a
big
strange is that CPU load only ~40% during the test.

  Maybe would be useful use own critical section like this:
http://www.codeproject.com/useritems/CritSectEx.asp
=20
Farid.