question on how cgminer figures intensity.
on dynamic with both 2.9.7.0/1 and 2.10.0 when I fire up folding@home on the cpu (which loads the 4 cores to 100%) cgminer drops intensity down to -8 or so on my 6870. stop folding and intensity goes to 4 or 5 where it should be.
cgminer times how long it takes for the gpu code to "return" after it's been given work. Unfortunately with windows, the timer resolution is so shithouse at 15ms that I have to sample many many iterations of the GPU code and then average them to see how long it took. This means that between giving the GPU code, there are short periods dependent on CPU code, and windows' scheduler does not seem to give this CPU code priority even though folding@home should be idle priority. So it ends up counting delays of the CPU scheduling as though the GPU had spent more time on its work. So it's a combination of the shit windows timer resolution and the shit windows scheduling that makes dynamic not work that well for your test case.
I LOVE the stratum support! dunno how you do it but cgminer just keeps getting better!
Thanks
