Thanks for the reply. Think I have a problem with GPU-Z. Dedicated stays at 0 MB, always. Dynamic is the only thing that changes.
I have a 2 GB card.
Well, with any card currently available, I think you get better performance with 1 thread, but for your card you will need to allocate 1.6 -1.7 GB to that thread. (double your TC to 28416 and adjust up or down from there). You're trying to cram a bunch of work into half the available memory - YACoin mining benefits from more memory - give it to it!
Thanks for the tip on HWInfo64 - I will point windows 8 folks to that tool.
--scan-time and --expiry : I don't set them, so whatever the default is.
Thing is, when I go higher than what's stated. It goes over to dynamic memory (I tried 16384 and it bombs). Think there's more in use than HWinfo states.
I'm on single thread, now. -R 512. I get some HW. But it seems OK.
Reason I ask about --scan-time and --expiry is of this link.
http://www.reddit.com/r/dogecoin/comments/1ui3bx/increase_such_hashrate_1_to_5_scrypt_tweaking/ceicnyvYou want both to be < block time, which is 60s for Dogecoin. Optimal values will take some playing around with relative to your hardware setup, but anything lower than the block time will result in an improvement in accepted shares (not hash rate, just better results from your hash rate). Generally I would say that expiry should be a little higher than scan time, and probably both should be 1/2 or less than the block time. You could start with values of 1 for each and work up, or maybe start at 30s or so for each and work down. The default values I believe are 120s expiry and 60s scantime based on 600s block time for bitcoin, so working off the same premise perhaps values of 12s expiry and 6s scantime would be the dogecoin analogue.
I know it's for Dogecoin. Isn't Yacoin 60s block time? Maybe stratum takes care of this for pools?
Learning as I go...
Show Posts
