comp.lang.ada
 help / color / mirror / Atom feed
From: Michael Erdmann <boavista@snafu.de>
Subject: Re: do ada tasks run accross 16 cpu boxs? or stuck on 1 cpu?
Date: Tue, 21 May 2013 21:41:20 +0200
Date: 2013-05-21T21:41:20+02:00	[thread overview]
Message-ID: <b020v1F1f2bU1@mid.uni-berlin.de> (raw)
In-Reply-To: <d3hvo89cml9bkno0pf98iipl3pg5ih6kci@invalid.netcom.com>

On 05/12/2013 06:35 PM, Dennis Lee Bieber wrote:
> On Sun, 12 May 2013 09:17:25 +0200, "ldries46" <bertus.dries@planet.nl>
> declaimed the following in comp.lang.ada:
>
>> I just have created my own program in which I originally did all ca;vulation
>> on one CPU. Now I created a part of the calculation in tasks running
>> paralel. On my four core systemI achieved a speed that exceded the original
>> speed by a factor of more than 3.  This meant three cores were running the
>> intensive calculation part in the tasks and one the administration around
>> the proces. (all with GNAT ADA on windows 7). The same exe file ran even
>> faster on a 4 core with hyperthreading machine of which the clock speed was
>> lower than that of the first test. I did nothing extraordinary to achieve
>> this.
>>
>
> 	I suspect you had a number cruncher application in which the intense
> code and most data all fit within each core's high-speed cache.
>
Try to bind your tasks to the CPU's and look at top (option 1). Then you 
can observe what your cpu's are doing. May be you should have a look at 
parafine :-)







  reply	other threads:[~2013-05-21 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 20:16 do ada tasks run accross 16 cpu boxs? or stuck on 1 cpu? johannes falcone
2013-05-07 20:29 ` Jeffrey Carter
2013-05-07 20:45   ` Ludovic Brenta
2013-05-07 23:10     ` johannes falcone
2013-05-08 13:13 ` john
2013-05-08 13:15   ` john
2013-05-12  7:17 ` ldries46
2013-05-12 16:35   ` Dennis Lee Bieber
2013-05-21 19:41     ` Michael Erdmann [this message]
2013-05-22 12:14       ` Marc C
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox