If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
well i realized that long time ago, but it make sense after all. Windows have been always very sicky in the way it handle threads(beside the horrible gut killing pain of sync them in the win32 thread api :* ). on the other hand posix threads have always seem extremely logical and stable in linux and other unix like oses too.
my bet here is that the poor performance in windows is due to hypertransport and the way cores are interconnected internally but is not AMD faults at the end is intel's/microsoft faults.
my bet is that somehow microsoft have some internal optimization in their thread api that force it to assume or add latency to compensate the heat produced for the old fsb system from intel, so that could ovbiuosly kill the benefit of Athlon/phenom/opteron hypertransport and inner memory manager due to the self generated latency.
now on the other hand could simple be that microsoft and intel have some hidden deal in there to slowdown amd chips internally so they make sure amd wont kill they processor in benchys by much, pretty much like the famous microsft/foxxcon bios "misunderstanding" from the g33 chipsets