See I'm even more a newbie than you. what does WU/s do or mean. I've reduced the VDDC on my 3 cards to 1100/1120/1100 ( the middle card was prevolted at 1225 the 1st and 3rd at 1175 stock which might explain why its needs a high VDDC to remain stable.
What kernel file do you use? I downloaded the 'optomised' .cl from your earlier post and put it in the kernel folder, but it always seems to use the "ckolivas.cl", if I only leave the optomised .cl file it won't work and putting in "kernel : scrypt130302" into my arguments means sgminer won't work.. so not sure what i'm doing there.
TC 8191 did seem to raise my hash rates up 707K/710kh/s its the blue bit that i'm taking that from. My numbers still seem to jump up and down alot though, does this watcher program help give you an average so you can tell if it really goes up?
WU/s = Work Utility / second. My understanding is that it's the actual usable data that your card is producing. You may be hashing at 740Kh/s but if your WU/s is 600, your card is doing 140Kh of nothing (except adding to the ambient temperature of your room and making your electric bill higher). But that's as much as I think I know (still a little fuzzy). Also I found this (explanation of cgminer interface), which is very helpful:
https://doges.org/index.php?topic=5101.0As far as the kernel goes, I simply renamed my existing kernel file "scrypt130511.cl" to "scrypt130511.cl.backup", and then copied the modified "scrypt130511.cl" file in to the same location as the backup. I didn't specify anything in my arguments, the miner just picks it up. Incidentally, how can you tell which .cl file the miner is using?
CGWatcher just gives you a nicer way to look at your stats, but I prefer to just look in the miner window since it's gives you immediate stats on what it's doing right that second. I primarily use CGWatcher because it can reboot the miner or even your computer if things crash. But it has a ton of other cool features like e-mail updates (which I just discovered yesterday, pretty cool). I notice that my hash rates jump up and down a lot in the first 15 or so minutes that the miner starts, so any time you make a change to your settings give it at least that long before determining if what you've changed helps or not. After it's been running for several hours the average rates should hardly change much at all. If it continues to jump around for a long time it may mean you're getting errors or lots of rejects (so I've heard).
That's as much as I know right now. Feel like I'll never be an expert at this though since there seem to be no end to the variables that can influence performance. Wish I were an engineer, alas I'm just a lay person trying to make a buck.