Quote from: rkinnin on April 29, 2015, 10:12:20 PM

Quote from: TracerX on April 28, 2015, 03:37:14 PM

Quote from: rkinnin on April 28, 2015, 01:43:38 PM

Quote from: vabchgent on April 24, 2015, 06:34:09 PM

I would set the p= in the password to 0.0110 to 0.0115 and let it roll. There have been spikes in SHA-256 the past 2 weeks at times to 30% over +.

i haven't played with the options like p= at all...but with the profit being -5% I thought I might. so I set one of my s3's to be p=.011, saved/applied and then rebooted.

I don't know if .011 is really a good value. would love peoples thoughts.

my s3 now shows that for westhash its "dead" and is mining at my secondary location. How often does the s3 check on the primary mining location, westhash, to see if it should switch back to westhash for mining?

thoughts are absolutely welcome.

I would use 0.0115 myself--nice/westhash charges a fee, so you want to make sure you take that into consideration. I use the calculator at bitcoinwisdom (on the diff page, top right) to determine what the 100% mark is per 1TH, then I bump that number up to make sure it's profitable. YMMV, but this will help you catch the crazy 30%+ rental fees without you worry about wasting hash when it's less profitable.

is the "port" still the same? :3334 ??

Correct, the port number does not change.