Author

Topic: CGwatcher causes hashrate to drop? (Read 1138 times)

sr. member
Activity: 840
Merit: 255
SportsIcon - Connect With Your Sports Heroes
January 25, 2014, 08:01:29 PM
#9
Same problem here, did you find any solution ?

not yet


Start cgminer in realtime priority. When setting up your profile in CgWatcher, click the "Advanced" button.
Run CgWatcher in idle priority. Either with task manager, Process Explorer or a batch file with the line @cmd /c "start /idle cgwatcher.exe"

If that doesn't solve, pool cgminer only each 10 seconds or so.

You guys are using single-core Sempron 145 CPUs, aren't you?

I'll give it a try, thanks.

Yes, I'm using a Sempron 145 single core
It figures...

That's a bad CPU if you want to run more than just cgminer. cgminer is advanced in prefetching work from pool and generating local work and generic multithreading and whatever more, however there's so much it can do on a single-core when it is frequently interrupted by cgwatcher, vnc server, network card interrupts, etc...

Cgwatcher could also be a bit more lightweight, but .net is very convenient...

Realtime priority improves some, but the suggestion you see everywhere of a Sempron 145, when there's a dual-core 190 for more $5, is frankly, pathetic.

I agree, I didn't realized how many things I was going to install and followed naively a guide buying the 145 sempron, although I was not convinced of the choice, but everyone seemed to point towards that CPU...
I regret that decision, I should not trust the "cheap" suggestions and spend a few bucks more
Yeah, I guess the 145 is ok if nothing else runs on the system. But I used cgwatcher, vnc server, teamviewer and some other software and noticed them using a few % cpu, so I knew that a single-core would make cgminer lag
hero member
Activity: 736
Merit: 508
January 25, 2014, 07:54:53 PM
#8
Same problem here, did you find any solution ?

not yet


Start cgminer in realtime priority. When setting up your profile in CgWatcher, click the "Advanced" button.
Run CgWatcher in idle priority. Either with task manager, Process Explorer or a batch file with the line @cmd /c "start /idle cgwatcher.exe"

If that doesn't solve, pool cgminer only each 10 seconds or so.

You guys are using single-core Sempron 145 CPUs, aren't you?

I'll give it a try, thanks.

Yes, I'm using a Sempron 145 single core
It figures...

That's a bad CPU if you want to run more than just cgminer. cgminer is advanced in prefetching work from pool and generating local work and generic multithreading and whatever more, however there's so much it can do on a single-core when it is frequently interrupted by cgwatcher, vnc server, network card interrupts, etc...

Cgwatcher could also be a bit more lightweight, but .net is very convenient...

Realtime priority improves some, but the suggestion you see everywhere of a Sempron 145, when there's a dual-core 190 for more $5, is frankly, pathetic.

I agree, I didn't realized how many things I was going to install and followed naively a guide buying the 145 sempron, although I was not convinced of the choice, but everyone seemed to point towards that CPU...
I regret that decision, I should not trust the "cheap" suggestions and spend a few bucks more
sr. member
Activity: 840
Merit: 255
SportsIcon - Connect With Your Sports Heroes
January 25, 2014, 07:44:52 PM
#7
Same problem here, did you find any solution ?

not yet


Start cgminer in realtime priority. When setting up your profile in CgWatcher, click the "Advanced" button.
Run CgWatcher in idle priority. Either with task manager, Process Explorer or a batch file with the line @cmd /c "start /idle cgwatcher.exe"

If that doesn't solve, pool cgminer only each 10 seconds or so.

You guys are using single-core Sempron 145 CPUs, aren't you?

I'll give it a try, thanks.

Yes, I'm using a Sempron 145 single core
It figures...

That's a bad CPU if you want to run more than just cgminer. cgminer is advanced in prefetching work from pool and generating local work and generic multithreading and whatever more, however there's so much it can do on a single-core when it is frequently interrupted by cgwatcher, vnc server, network card interrupts, etc...

Cgwatcher could also be a bit more lightweight, but .net is very convenient...

Realtime priority improves some, but the suggestion you see everywhere of a Sempron 145 to handle $2000 worth of videocards, when there's a dual-core 190 for more $5, is frankly, pathetic.
hero member
Activity: 736
Merit: 508
January 25, 2014, 06:17:33 PM
#6
Same problem here, did you find any solution ?

not yet


Start cgminer in realtime priority. When setting up your profile in CgWatcher, click the "Advanced" button.
Run CgWatcher in idle priority. Either with task manager, Process Explorer or a batch file with the line @cmd /c "start /idle cgwatcher.exe"

If that doesn't solve, pool cgminer only each 10 seconds or so.

You guys are using single-core Sempron 145 CPUs, aren't you?

I'll give it a try, thanks.

Yes, I'm using a Sempron 145 single core
sr. member
Activity: 840
Merit: 255
SportsIcon - Connect With Your Sports Heroes
January 25, 2014, 05:50:21 PM
#5
Start cgminer in realtime priority. When setting up your profile in CgWatcher, click the "Advanced" button.
Run CgWatcher in idle priority. Either with task manager, Process Explorer or a batch file with the line @cmd /c "start /idle cgwatcher.exe"

If that doesn't solve, pool cgminer only each 10 seconds or so.

You guys are using single-core Sempron 145 CPUs, aren't you?
hero member
Activity: 908
Merit: 503
January 25, 2014, 05:47:12 PM
#4
Same problem here, did you find any solution ?
hero member
Activity: 736
Merit: 508
January 13, 2014, 07:13:15 PM
#3
After two days changing settings, miner arguments, switching between .bat or .conf files, trying different cgwatcher versions, it comes out that it is the Monitor feature to cause this issue.
Enabling monitoring every 10 seconds for example, when the graph and the stats are updated, the hashrate drops instaneously about 40-50 KH/s (per gpu) and continuing to drop for about 1-2 seconds, then the hashrate recovers until the next monitor update.

I tried to edit the delay of the refresh but this of course only postpones the problem, currently I'm using 30 minutes and although this setting allows the average hashrate to decrease almost imperceptibly, I'm worried that a GPU becomes sick or something goes bad in those 30 minutes...
Obviously disabling the monitor solves this issue but CGWatcher without monitor loses a lot :\
full member
Activity: 121
Merit: 100
January 12, 2014, 10:54:40 PM
#2




I have been having issues also. I just re-installed cgminer and re-initialized the config in cgwatcher.... seems a little better now
hero member
Activity: 736
Merit: 508
January 12, 2014, 10:24:57 PM
#1

I noticed when I start cgminer with CGWatcher, my hashrate is lower and HIGHLY more unstable.
Usually it grows to his peaks and then drops for about 80-120 KH/s per gpu, then it grows again and drops again, and so on every few seconds.
Apart from that the overall hashrate is lower, starting cgminer directly I get from my gpus an average of 750 Kh/s per card, starting from CGWatcher my average is about 710 KH/s per card.


There are my settings:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *.bin
cgminer.exe --scrypt -w 256 -v 1 -I 13 -g 2 --lookup-gap 2 --thread-concurrency 8192 --gpu-memclock 1500,1500,1800,1800 --gpu-engine 1080,1080,1120,1120 --gpu-fan 30-70 --temp-overheat 86 --temp-cutoff 90 --auto-fan



any ideas?
Your CGWatcher leaks your hashrate, too?
Jump to: