Poster: Iriel at 8/22/2006 10:01:15 PM PDT
Subject: Dual core Athlon problem with profile timing |
| |
I've been able to verify an earlier-reported problem with debugprofilestop() and dual core processors. That APPEARS to be the problem, because i've had a bunch of people run tests and the dual core athlon folks are seeing consistent results with me.
The simple test is
/script debugprofilestart() message(debugprofilestop())
Expected results are numbers like: 0.00029628
"Problem" results are numbers like: 978
Both problem observations were made on Socket AM2 Athlon64 X2 processors (Mine specifically is: AMD Athlon 64 X2 4600+ Windsor 2000MHz HT Socket AM2 Dual Core Processor)
Valid results have been seen on P4 HT, and single core Athlon64 processors.[ post edited by Iriel ]
UI & Macro Forum MVP Understand GC!
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=435691&p=#post435691 |
| |
Poster: slouken at 8/23/2006 9:09:37 PM PDT
Subject: Re: Dual core Athlon problem with profile timing |
| |
Confirmed. The code doesn't work properly on multi-core systems at the moment, since it reads the CPU time stamp counter directly.
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=435691&p=#post436797 |
