Tír Na HiFi

Engine fire, eh? Ouch!

sebna wrote:Hi Nige,

WinTimerTester is the name :) - the optimal result should be around 1.4mhz in this one.

Have to check the one which you posted.

Can you post screenshot from Latmon.

Thanks

Apologies for flooding the page heres for the asus and the old p67 gigabyte build (rip)

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 1:17:59 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: WIN-6NLPE6NGTKP
OS version: Windows Server 2012 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., P8Z77-M
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16065 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 1600.0 MHz
Measured CPU speed: 1044.0 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 133.676207
Average measured interrupt to process latency (µs): 10.266911

Highest measured interrupt to DPC latency (µs): 128.787318
Average measured interrupt to DPC latency (µs): 3.947576


_________________________________________________________________________________________________________
MEASURED SMI, IPI AND CPU STALLS
_________________________________________________________________________________________________________
The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.

Highest measured SMI or CPU stall (µs) 4.469842


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 49.690
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.000345
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.000503

ISR count (execution time <250 µs): 112698
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 174.950
Driver with highest DPC routine execution time: netbt.sys - MBT Transport driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.151455
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0.241645

DPC count (execution time <250 µs): 16919079
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.


Process with highest pagefault count: latmon.exe

Total number of hard pagefaults 2
Hard pagefault count of hardest hit process: 1
Highest hard pagefault resolution time (µs): 1014.80750
Total time spent in hard pagefaults (%): 0.000005
Number of processes hit: 2


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 162.838077
CPU 0 ISR highest execution time (µs): 49.690
CPU 0 ISR total execution time (s): 0.188357
CPU 0 ISR count: 112698
CPU 0 DPC highest execution time (µs): 120.0350
CPU 0 DPC total execution time (s): 59.816406
CPU 0 DPC count: 15697166
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 83.962580
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 65.6550
CPU 1 DPC total execution time (s): 0.005182
CPU 1 DPC count: 1511
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 61.626594
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 76.30
CPU 2 DPC total execution time (s): 0.041579
CPU 2 DPC count: 7530
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 86.082703
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 39.2650
CPU 3 DPC total execution time (s): 0.001728
CPU 3 DPC count: 674
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 117.957045
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 69.03250
CPU 4 DPC total execution time (s): 0.025428
CPU 4 DPC count: 7195
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 282.894883
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 69.05250
CPU 5 DPC total execution time (s): 30.406242
CPU 5 DPC count: 1178942
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 156.774245
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 174.950
CPU 6 DPC total execution time (s): 0.046570
CPU 6 DPC count: 12513
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 232.414601
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 168.1350
CPU 7 DPC total execution time (s): 0.111083
CPU 7 DPC count: 13548
_________________________________________________________________________________________________________

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:05:14 (h:mm:ss) on processors 0 and 1.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: JPLAYENT
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: Gigabyte Technology Co., Ltd., P67A-UD3-B3
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Logical processors: 8
Processor groups: 1
RAM: 8154 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3410.0 MHz
Measured CPU speed: 2265.0 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 28.527672
Average measured interrupt to process latency (µs): 2.079703

Highest measured interrupt to DPC latency (µs): 27.326507
Average measured interrupt to DPC latency (µs): 0.468717


_________________________________________________________________________________________________________
MEASURED SMI, IPI AND CPU STALLS
_________________________________________________________________________________________________________
The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.

Highest measured SMI or CPU stall (µs) 0.600583


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 13.249267
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.002178
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.002251

ISR count (execution time <250 µs): 297619
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 114.559531
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.062461
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.078368

DPC count (execution time <250 µs): 1089383
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.


Process with highest pagefault count: services.exe

Total number of hard pagefaults 5
Hard pagefault count of hardest hit process: 4
Highest hard pagefault resolution time (µs): 546.129912
Total time spent in hard pagefaults (%): 0.000072
Number of processes hit: 1


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2.744983
CPU 0 ISR highest execution time (µs): 13.249267
CPU 0 ISR total execution time (s): 0.056587
CPU 0 ISR count: 297619
CPU 0 DPC highest execution time (µs): 114.559531
CPU 0 DPC total execution time (s): 1.969501
CPU 0 DPC count: 1089329
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.395254
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 14.152493
CPU 1 DPC total execution time (s): 0.000283
CPU 1 DPC count: 54
_________________________________________________________________________________________________________

Thanks Nige,

I heard that some of Gigabyte MBs are even better then Asus ones but the readings from your P67A-UD3-B3 are pretty amazing.

You did not post few last lines - how ling did you run the test on P67A-UD3-B3?

Anyway Asus readings are also top notch.

Thanks

ran the gigabyte for only five min, i usually build with giabyte, i couldn't find one this time to fit my case with a compatible ethernet adapter

tried to downsize my power supplies (trilinear) down to one (Maplin linear) using http://www.ebay.com/itm/400293000788?ss ... 1439.l2649 to supply 5v to usb3 windows to go bringing three cables from the maplin one to cpu one to pico and one to the voltage regulator for usb3.

testing done with single pc
underclocked cpu to 1.6 ram to 800
trilinear supply as benchmark
core server 2012

results were very disappointing not only did i downsize the power supplies but the dynamics, bass weight and vocal and instrumental separation (air) as well.

i tried several combinations using a separate supply for cpu then pico then usb3, in each instance their was an improvement
when using all separate supplies the result was profound.

if i couldn't reduce the size/amount of power supplies without loosing sound quality ill try to reduce the cost i would be fairly certain that this configuration will yeild similar results.

two of these http://www.maplin.co.uk/13.8v-regulated ... cification XM20W supplies adjusted to supply 12v to cpu and pico psu along with a wall wart supplying 5v 1 amp is plenty for usb3

it is important to remember that the single linear supply usb3 wtg builds we have been working on are in the league with high end cd players.
separating of the power supplies , jplay, core server 2012, usb3 windows to go and a underclocked pc accompanied with a good dac most likely will rival any source
especially with high resolution material.

I can vouch for the sound of the maplins when powering the zuma separately. Sound was better than the single supply into my zuma.
Maybe I have posted this already but too lazy to go back checking. We tried out my zuma with intel mobo and same spec as Nigels with exception of two things. I hadn't underclocked my ram and the mob in Nigels is a higher spec asus. Sound with the 3 maplins was best. When Nigel removed the supplies to make all things equal except mobo and underclocked ram the gap closed but on the day we both thought the asus zuma had a little bit extra. Personally I am convinced to get that extra bit you have to separate the supplies out. In reality it is only for those who want to go to the ends of the earth as the difference is not huge. The 3 supplies obviously cause more clutter and the diy contraptions + bought bits to make it all happen look like a dogs dinner(sorry nigel)

Oh and core server moves things on again. My usb stick (well I didn't construct it) was stolen away by another tirnihifer for testing. Definitely the way to go if wanting to get the best output from the pc. I am back working on WTG stick tonight and it sounds mighty fine as well.

Will have to do a bit of practicing with the soldering iron during the winter as the improvements achieved by the Nige's would cost at most a €100 to achieve

tony wrote:I can vouch for the sound of the maplins when powering the zuma separately. Sound was better than the single supply into my zuma.
Maybe I have posted this already but too lazy to go back checking. We tried out my zuma with intel mobo and same spec as Nigels with exception of two things. I hadn't underclocked my ram and the mob in Nigels is a higher spec asus. Sound with the 3 maplins was best. When Nigel removed the supplies to make all things equal except mobo and underclocked ram the gap closed but on the day we both thought the asus zuma had a little bit extra. Personally I am convinced to get that extra bit you have to separate the supplies out. In reality it is only for those who want to go to the ends of the earth as the difference is not huge. The 3 supplies obviously cause more clutter and the diy contraptions + bought bits to make it all happen look like a dogs dinner(sorry nigel)

Oh and core server moves things on again. My usb stick (well I didn't construct it) was stolen away by another tirnihifer for testing. Definitely the way to go if wanting to get the best output from the pc. I am back working on WTG stick tonight and it sounds mighty fine as well.

Will have to do a bit of practicing with the soldering iron during the winter as the improvements achieved by the Nige's would cost at most a €100 to achieve

i hadn't finished testing when i was with you thats why its rough and ready for all the a-b testing and it does all need a right bit of tidying up, i asked what you thought of the sound not what it looked like, its a working progress

most of us that has gone down this road has got a linear supply already its just another one beside it and another wall wart and a usb3 mod.

the trilinear was great for testing but the maplin type supplies would be more practical and cost effective.

Just think what most people will think of 3 linear maplin supplies for one pc and then another one for the dac. That is 4 supplies compared to 1 for a CDP. Ah Ok it sounded gorgeous and didn't look too bad either.

FWIW, its always this way at the coalface!!!!

I literally have had valve amps sitting in carboard boxes on test before building somewhat more neatly in a chassis!! The neat looks only come after all the investigating is done.....

My own rule now is that if it looks "ok" and is at least safe - ie kids can't easily get access to HV, then that's fine by me.......


do this:



to get this:

Yes, the sound of the Core Server stick is a major leap even from the WTG stick with Cad's script. The bass is meatier but not bloated, vocals are more distinct and the top notes are sweet. A real improvement and I was surprised that it worked first time without any ipconfigging etc. Thanks Tony :).
KM