schizobeyondpills wrote: ↑29 Oct 2020, 10:07
O_O wrote: ↑27 Oct 2020, 07:51
schizobeyondpills wrote: ↑17 Oct 2020, 08:32
Windows kernel timer has a limit of 0.5 ms interrupt intervals.
What does that have to do with 8K polling rate?
its an indicator that windows is not engineered for such high performance devices, its not hard to see or figure out, where do you have problems with? do you need further help? RTC and HPET allow far lower interrupt intervals than 0.5ms but Windows does not implement them intentionally due to being very badly engineered outdated kernel which is not optimized to handle such high freq interrupts.
look at
https://forums.guru3d.com/threads/windo ... ng.377790/
then at
https://www.compuphase.com/int70.txt which is RTC clock freq, for example, windows is limited to 0.4992ms interrupt interval however any RTC clock can do 8kHz interrupt intervals, but windows doesnt allow u to do this unless you patch it (yes i did it, yes it feels amazing vs 0.5ms cripple limit)
Code: Select all
Periodic Interrupt
==================
The frequency of this interrupt is programmable from 2 to 8192 per
second. To use this type of interrupt first set RS (Rate Select)
bits in Status Register A to the required value:
RS Int/sec Period
3210 - -
0000 none none
0001 256 3.90625 ms
0010 128 7.8125 ms
0011 8192 122.070 Micros
0100 4096 244.141 Micros
0101 2048 488.281 Micros
0110 1024 976.562 Micros
0111 512 1.93125 ms
1000 256 3.90625 ms
1001 128 7.8125 ms
1010 64 15.625 ms
1011 32 31.25 ms
1100 16 62.50 ms
1101 8 125.0 ms
1110 4 250.0 ms
1111 2 500.0 ms
notice the 488.281 micros, which is exactly what u will get if u disable HPET and use windows API to set timer to 0.5ms, or 0.488ms =)
windows is not engineered for high performance computers operating on constant clock at 4GHz+ per core so they dont allow you to set it all the way up to 8kHz.
same goes for HPET and other sources,
https://wiki.osdev.org/Timer_Interrupt_Sources#HPET they are all crippled within windows being targeted at laptop users and casual desktop.
"Rate" is the divider setting. If you select a rate of 1 or 2, the RTC will have problems and "roll over" so that it generates interrupts of .81 mS and 3.91 mS, rather than the expected interrupts of 61.0 uS or 30.5 uS. So, the fastest rate you can select is 3. This will generate interrupts of 8 kHz or 122 uS.
>Percentage is going to be lower than that I think but just like you generally wouldn't pair a top end graphics card with a low end CPU, 8K isn't for everyone and some programs may choke.
not programs but systems, big difference. only top 0.000001% of PCs will have actual stable 8000Hz (that means looking at few digits past the decimal seperator )
>No, 40C is maximum recommended ambient temperature, the temperature of the air near the sensor while absolute ambient temperature is likely 15C higher than that. USB polling will be taken care of by the MCU which might be a LPC11U3... which has an ambient specification of -40C to 85C and a maximum junction temperature of 150C.
Thats just the "recommended" spec which does not reveal real life measures of usage under closed shell on a nanosecond/ps scale graph of performance, something "working" doesnt mean its working properly, just as a human being can run but it starts to fall apart, doesnt mean its working optimally. just "working"
>Temperature is a result of power dissipation and dynamic power is proportional as voltage is constant.
yeah but u forgot the biggest two factors of power dissipation, scaling of frequency and size of both transistors/IC in nanometers, COMBINED.
>This is the system timer and operates from around 0.5ms to 15.6ms, it is not windows time.
it is literally the source of time within the whole OS.
The system’s clock interval timer is probably the most important device on a Windows machine, as evidenced by its high IRQL value (CLOCK_LEVEL) and due to the critical nature of the work it is responsible for. Without this interrupt, Windows would lose track of time, causing erroneous results in calculations of uptime and clock time—and worse, causing timers not to expire anymore and threads never to lose their quantum anymore. Windows would also not be a preemptive operating system, and unless the current running thread yielded the CPU, critical background tasks and scheduling could never occur on a given processor.
^ from Windows Internals. try again please
its very sad that so many of you are very attached to marketing buzzwords rather than verifying those claims yourself.
reality has more depth than what you can perceive, it is not a single layer of "good" or "bad". the layers are infinite in depth, and reasoning about them absolutely does NOT start at a single layer. only a blind fool would do that.
also,please, PLEASE, stop mixing up timers and clock. its a big difference, timers are events at certain periodic intervals, clock is the source of time, tyvm.
@Chief
15 years of Moore’s Law on USB processing.
Moore's Law has nothing to do with whats implemented in reality, just as Intel is selling same cores for 10 years (Ivy Bridge CORE). Sure, moore's law has atom sized transistors, but Intel bounced off 10nm into 14nm, after being there for +++++ generations