I have a program that runs an "easily" parallelizable loop. When I run it as a single thread it only takes about 10% longer than 2 threads (on a dual-core). I'm trying to track down the lossed time and am wondering if turning on -profile is even worth looking at. The concern is that it might not be thread safe or might just skew the result so much as to be useless.

Hello BCS,

> I have a program that runs an "easily" parallelizable loop. When I run
> it as a single thread it only takes about 10% longer than 2 threads
> (on a dual-core). I'm trying to track down the lossed time and am
> wondering if turning on -profile is even worth looking at. The concern
> is that it might not be thread safe or might just skew the result so
> much as to be useless.
> 

Well it seems that runing threded code with -profile gives a seg-v. So I guess that answers that.

BCS wrote:
> Hello BCS,
> 
>> I have a program that runs an "easily" parallelizable loop. When I run it as a single thread it only takes about 10% longer than 2 threads (on a dual-core). I'm trying to track down the lossed time and am wondering if turning on -profile is even worth looking at. The concern is that it might not be thread safe or might just skew the result so much as to be useless.
>>
> 
> Well it seems that runing threded code with -profile gives a seg-v. So I guess that answers that.
> 
> 

Try GDC. :)

BCS wrote:

> Hello BCS,
> 
>> I have a program that runs an "easily" parallelizable loop. When I run it as a single thread it only takes about 10% longer than 2 threads (on a dual-core). I'm trying to track down the lossed time and am wondering if turning on -profile is even worth looking at. The concern is that it might not be thread safe or might just skew the result so much as to be useless.
>> 
> 
> Well it seems that runing threded code with -profile gives a seg-v. So I guess that answers that.

See last comment of Walter: http://d.puremagic.com/issues/show_bug.cgi?id=971