Bitcoin Forum
December 06, 2016, 08:00:23 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 [413] 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 ... 830 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.9.2  (Read 4820085 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Askit2
Hero Member
*****
Offline Offline

Activity: 524


View Profile
November 27, 2012, 12:14:54 AM
 #8241

Throwing out work with every notify message on stratum, which comes on average every 30 seconds, would have the same effect as a longpoll every 30 seconds. That's a lot of work to discard midstream. Why on earth would there even be a clean_work method with stratum if every notify implied we throw out the work?
You're not supposed to throw out the shares on LPs. Restarting work has no cost except on BFLs (where you have a bug that loses valid shares).

So Junior is saying my reject ~9minutes into the block is because CGMiner didn't change to new work fast enough?
That sounds highly unlikely, and unrelated. What kind of a reject?

Top post on the page you are asking on. LOOK UP!

I appreciate donations at ( 1NwkQdmomQPLtdes5KuZhB1D22p7ZGRy4p )
If I am helping in the CGMiner thread give it to Con or Kano. They do the work there.
If you want to sign up for a coinbase account I would appreciate it if you use my referral link. US people now wire, 1% fee give or take a little for sending to your bank account. https://coinbase.com/?r=515bf6145682db9d11000028&utm_campaign=user-referral&src=
1481054423
Hero Member
*
Offline Offline

Posts: 1481054423

View Profile Personal Message (Offline)

Ignore
1481054423
Reply with quote  #2

1481054423
Report to moderator
1481054423
Hero Member
*
Offline Offline

Posts: 1481054423

View Profile Personal Message (Offline)

Ignore
1481054423
Reply with quote  #2

1481054423
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481054423
Hero Member
*
Offline Offline

Posts: 1481054423

View Profile Personal Message (Offline)

Ignore
1481054423
Reply with quote  #2

1481054423
Report to moderator
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
November 27, 2012, 12:22:33 AM
 #8242

Throwing out work with every notify message on stratum, which comes on average every 30 seconds, would have the same effect as a longpoll every 30 seconds. That's a lot of work to discard midstream. Why on earth would there even be a clean_work method with stratum if every notify implied we throw out the work?
You're not supposed to throw out the shares on LPs. Restarting work has no cost except on BFLs (where you have a bug that loses valid shares).

So Junior is saying my reject ~9minutes into the block is because CGMiner didn't change to new work fast enough?
That sounds highly unlikely, and unrelated. What kind of a reject?

Top post on the page you are asking on. LOOK UP!
Luke-Jr thank you for yet again pointing out why people who use your miner get less shares Tongue (and shouldn't be using it)
Yeah processing previous block work after an LP ... right ... ... ...

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
Luke-Jr
Legendary
*
Offline Offline

Activity: 2086



View Profile
November 27, 2012, 12:39:17 AM
 #8243

Throwing out work with every notify message on stratum, which comes on average every 30 seconds, would have the same effect as a longpoll every 30 seconds. That's a lot of work to discard midstream. Why on earth would there even be a clean_work method with stratum if every notify implied we throw out the work?
You're not supposed to throw out the shares on LPs. Restarting work has no cost except on BFLs (where you have a bug that loses valid shares).

So Junior is saying my reject ~9minutes into the block is because CGMiner didn't change to new work fast enough?
That sounds highly unlikely, and unrelated. What kind of a reject?

Top post on the page you are asking on. LOOK UP!
Ok, I missed that somehow. "unknown-work" can only occur if one of these 3 cases:
  • a block was found (which you ruled out)
  • the miner submitted it after it expired (120 seconds on EMC; new work is delivered at least every 96 seconds)
  • the user extranonce1 was lost (only possible if you reconnected)
I'm pretty sure cgminer discards all work/shares in the last case (reconnection), so that means it either:
  • was working on a job 23 seconds after it had been replaced (this is sufficient for as low as 200 Mh/s)
  • was working on a job 21 seconds after it had been replaced AND took over 2 seconds to submit it to the pool
This makes sense, since cgminer is failing to move on to new jobs as they come in.

mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
November 27, 2012, 12:51:51 AM
 #8244

Just adding my 0.0016 BTC worth here..

Since p2pool has gone berserk, I have half my miners pointing at EMC, and half at Oz.

Oz is using stratum.
EMC is using GBT.

After about 12 hours, there were noticeably more rejects on EMC than on Oz.  That's with using GBT, not stratum, on Oz.

Not sure if it means anything.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Askit2
Hero Member
*****
Offline Offline

Activity: 524


View Profile
November 27, 2012, 12:58:56 AM
 #8245

Throwing out work with every notify message on stratum, which comes on average every 30 seconds, would have the same effect as a longpoll every 30 seconds. That's a lot of work to discard midstream. Why on earth would there even be a clean_work method with stratum if every notify implied we throw out the work?
You're not supposed to throw out the shares on LPs. Restarting work has no cost except on BFLs (where you have a bug that loses valid shares).

So Junior is saying my reject ~9minutes into the block is because CGMiner didn't change to new work fast enough?
That sounds highly unlikely, and unrelated. What kind of a reject?

Top post on the page you are asking on. LOOK UP!
Ok, I missed that somehow. "unknown-work" can only occur if one of these 3 cases:
  • a block was found (which you ruled out)
  • the miner submitted it after it expired (120 seconds on EMC; new work is delivered at least every 96 seconds)
  • the user extranonce1 was lost (only possible if you reconnected)
I'm pretty sure cgminer discards all work/shares in the last case (reconnection), so that means it either:
  • was working on a job 23 seconds after it had been replaced (this is sufficient for as low as 200 Mh/s)
  • was working on a job 21 seconds after it had been replaced AND took over 2 seconds to submit it to the pool
This makes sense, since cgminer is failing to move on to new jobs as they come in.

So a BFL single running 864mhash bitstream in your example would need to work on the work for 114.8 seconds to go over. Interesting to know.
I didn't change scan time for stratum but the settings of scan time at 115 had worked fine on get work.

I will bump it down but since not every 120 seconds has this happening I would assume it is something else. The ping to Eclipse is 76ms right now. It can vary but assuming I got my work at 96 seconds add .5 for significant delays, 5.16s for single to process work I get 101.66 seconds. Leaving me 18.34 seconds to submit.....

I appreciate donations at ( 1NwkQdmomQPLtdes5KuZhB1D22p7ZGRy4p )
If I am helping in the CGMiner thread give it to Con or Kano. They do the work there.
If you want to sign up for a coinbase account I would appreciate it if you use my referral link. US people now wire, 1% fee give or take a little for sending to your bank account. https://coinbase.com/?r=515bf6145682db9d11000028&utm_campaign=user-referral&src=
Luke-Jr
Legendary
*
Offline Offline

Activity: 2086



View Profile
November 27, 2012, 01:03:03 AM
 #8246

Throwing out work with every notify message on stratum, which comes on average every 30 seconds, would have the same effect as a longpoll every 30 seconds. That's a lot of work to discard midstream. Why on earth would there even be a clean_work method with stratum if every notify implied we throw out the work?
You're not supposed to throw out the shares on LPs. Restarting work has no cost except on BFLs (where you have a bug that loses valid shares).

So Junior is saying my reject ~9minutes into the block is because CGMiner didn't change to new work fast enough?
That sounds highly unlikely, and unrelated. What kind of a reject?

Top post on the page you are asking on. LOOK UP!
Ok, I missed that somehow. "unknown-work" can only occur if one of these 3 cases:
  • a block was found (which you ruled out)
  • the miner submitted it after it expired (120 seconds on EMC; new work is delivered at least every 96 seconds)
  • the user extranonce1 was lost (only possible if you reconnected)
I'm pretty sure cgminer discards all work/shares in the last case (reconnection), so that means it either:
  • was working on a job 23 seconds after it had been replaced (this is sufficient for as low as 200 Mh/s)
  • was working on a job 21 seconds after it had been replaced AND took over 2 seconds to submit it to the pool
This makes sense, since cgminer is failing to move on to new jobs as they come in.

So a BFL single running 864mhash bitstream in your example would need to work on the work for 114.8 seconds to go over. Interesting to know.
No, that 21-23 seconds is real time. No matter what hashrate. 200 Mh/s is the hashrate where if you are any slower, you might still be working on the old work normally.

Askit2
Hero Member
*****
Offline Offline

Activity: 524


View Profile
November 27, 2012, 01:14:24 AM
 #8247

ok so
96+ 23 = 119
114.8+5.2=119
Was my point. Maybe it's the maths...

Looking at it another way. I have 119 seconds or your 23 seconds should be 24 seconds to hash the work unit, find shares, and return those shares for money.

The 120 seconds is only to add either a second for submission or isn't in existance.

This left me wondering why you said 120 seconds to start with and only had math to make 119. Possibly to account for round trip delays or the share validation. You didn't really say. So either your math was off, or you left out part of your math.

Expiry still at 120
scan time adjusted to 95
Same Unknown Work

I appreciate donations at ( 1NwkQdmomQPLtdes5KuZhB1D22p7ZGRy4p )
If I am helping in the CGMiner thread give it to Con or Kano. They do the work there.
If you want to sign up for a coinbase account I would appreciate it if you use my referral link. US people now wire, 1% fee give or take a little for sending to your bank account. https://coinbase.com/?r=515bf6145682db9d11000028&utm_campaign=user-referral&src=
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
November 27, 2012, 01:19:25 AM
 #8248

Throwing out work with every notify message on stratum, which comes on average every 30 seconds, would have the same effect as a longpoll every 30 seconds. That's a lot of work to discard midstream. Why on earth would there even be a clean_work method with stratum if every notify implied we throw out the work?
You're not supposed to throw out the shares on LPs. Restarting work has no cost except on BFLs (where you have a bug that loses valid shares).

So Junior is saying my reject ~9minutes into the block is because CGMiner didn't change to new work fast enough?
That sounds highly unlikely, and unrelated. What kind of a reject?

Top post on the page you are asking on. LOOK UP!
Ok, I missed that somehow. "unknown-work" can only occur if one of these 3 cases:
  • a block was found (which you ruled out)
  • the miner submitted it after it expired (120 seconds on EMC; new work is delivered at least every 96 seconds)
  • the user extranonce1 was lost (only possible if you reconnected)
I'm pretty sure cgminer discards all work/shares in the last case (reconnection), so that means it either:
  • was working on a job 23 seconds after it had been replaced (this is sufficient for as low as 200 Mh/s)
  • was working on a job 21 seconds after it had been replaced AND took over 2 seconds to submit it to the pool
This makes sense, since cgminer is failing to move on to new jobs as they come in.

So a BFL single running 864mhash bitstream in your example would need to work on the work for 114.8 seconds to go over. Interesting to know.
I didn't change scan time for stratum but the settings of scan time at 115 had worked fine on get work.

I will bump it down but since not every 120 seconds has this happening I would assume it is something else. The ping to Eclipse is 76ms right now. It can vary but assuming I got my work at 96 seconds add .5 for significant delays, 5.16s for single to process work I get 101.66 seconds. Leaving me 18.34 seconds to submit.....
Please just ignore Luke-Jr.
Most of what he says is FUD and even if it's not all FUD - having to waste time wading through it all is just that - a waste of time.
His answer will simply be - you must use his miner coz it does it properly ... lulz

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
Luke-Jr
Legendary
*
Offline Offline

Activity: 2086



View Profile
November 27, 2012, 02:23:46 AM
 #8249

ok so
96+ 23 = 119
114.8+5.2=119
Was my point. Maybe it's the maths...
You're not supposed to stop at 5.2 seconds. Stratum jobs can be used infinitely, until the block is invalid or the pool expires the job. Unlike getwork, there is no 232 nonce limit.

This left me wondering why you said 120 seconds to start with and only had math to make 119. Possibly to account for round trip delays or the share validation. You didn't really say. So either your math was off, or you left out part of your math.
I subtracted a second for the time between the pool sending the job and you receiving it.

P.S. Kano is simply a liar, as usual.

crazyates
Legendary
*
Offline Offline

Activity: 938



View Profile
November 27, 2012, 02:30:45 AM
 #8250

Please just ignore Luke-Jr.
P.S. Kano is simply a liar, as usual.
I feel like I've read this thread before. Maybe I'm psychic?!

Either way, it's been rough trying to keep up with all of you on the work being done to stratum and CGMiner, but keep it up!

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
November 27, 2012, 02:49:54 AM
 #8251

Please just ignore Luke-Jr.
P.S. Kano is simply a liar, as usual.
I feel like I've read this thread before. Maybe I'm psychic?!

Either way, it's been rough trying to keep up with all of you on the work being done to stratum and CGMiner, but keep it up!
Stratum and CGMiner is fine.
The minor issues with Stratum are that shares can be lost.

However, that number is already WAY lower than using GetWork or Moron's piece of shit.
Yes it is important to understand that.

I've been going on about the Stratum issue for quite a while.
(ckolivas actually mentioned it to them first, but I didn't know that until shortly after I brought it up)

I'd like to get no Rejects per day.
At the moment with Stratum on OzCoin with a fixed 8 difficulty and ignoring reconnects (that I force each day at midnight) I get 1 reject each day with 1.6GH/s
Yes I'm bitching about getting 1 reject each day Tongue
I want 0 Smiley

This I guess is part of the reason why slush has ignored my request ... but in the end he's trying to implement a fix on the mistake he's made rather than just simply fixing it and ignoring the so called necessary backwards compatibility Sad
It's not been around long enough to care about backwards compatibility with a mistake.

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
crazyates
Legendary
*
Offline Offline

Activity: 938



View Profile
November 27, 2012, 03:04:09 AM
 #8252

Yep I'm on CGMiner 2.9.5, with stratum on Ozcoin. I set the diff to 2 with 1.5GH/s, and today I'm just under 0.3% rejects, which is actually pretty high. I'm usually around 0.1-0.2%. Cheesy

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
November 27, 2012, 03:08:58 AM
 #8253

Yep I'm on CGMiner 2.9.5, with stratum on Ozcoin. I set the diff to 2 with 1.5GH/s, and today I'm just under 0.3% rejects, which is actually pretty high. I'm usually around 0.1-0.2%. Cheesy
Those rejects are 99% likely to be either during connect while the difficulty corrects itself (directly related to the problem being discussed) or due to reconnects (i.e. if you lose pool connection)

The fix for the 2nd one (reconnects) is simply an enhancement ... that no doubt there will be few arguments about (when it gets in vogue Tongue) since it is just an enhancement - no compatibility issue with the current implementation.

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
crazyates
Legendary
*
Offline Offline

Activity: 938



View Profile
November 27, 2012, 03:23:04 AM
 #8254

Yep I'm on CGMiner 2.9.5, with stratum on Ozcoin. I set the diff to 2 with 1.5GH/s, and today I'm just under 0.3% rejects, which is actually pretty high. I'm usually around 0.1-0.2%. Cheesy
Those rejects are 99% likely to be either during connect while the difficulty corrects itself (directly related to the problem being discussed) or due to reconnects (i.e. if you lose pool connection)

The fix for the 2nd one (reconnects) is simply an enhancement ... that no doubt there will be few arguments about (when it gets in vogue Tongue) since it is just an enhancement - no compatibility issue with the current implementation.
Ya my first several shares are usually rejects. I am mining over wifi, with about a dozen+ other computers on the network, so DCs are a fact of life. Still, I can live with 0.3% for now. Wink

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
hahahafr
Sr. Member
****
Offline Offline

Activity: 241



View Profile
November 27, 2012, 03:45:48 AM
 #8255

Yep I'm on CGMiner 2.9.5, with stratum on Ozcoin. I set the diff to 2 with 1.5GH/s, and today I'm just under 0.3% rejects, which is actually pretty high. I'm usually around 0.1-0.2%. Cheesy
Those rejects are 99% likely to be either during connect while the difficulty corrects itself (directly related to the problem being discussed) or due to reconnects (i.e. if you lose pool connection)

The fix for the 2nd one (reconnects) is simply an enhancement ... that no doubt there will be few arguments about (when it gets in vogue Tongue) since it is just an enhancement - no compatibility issue with the current implementation.
Ya my first several shares are usually rejects. I am mining over wifi, with about a dozen+ other computers on the network, so DCs are a fact of life. Still, I can live with 0.3% for now. Wink

Don't go further. This is the issue.

sharky112065
Sr. Member
****
Offline Offline

Activity: 383



View Profile
November 27, 2012, 03:50:29 AM
 #8256

Yep I'm on CGMiner 2.9.5, with stratum on Ozcoin. I set the diff to 2 with 1.5GH/s, and today I'm just under 0.3% rejects, which is actually pretty high. I'm usually around 0.1-0.2%. Cheesy
Those rejects are 99% likely to be either during connect while the difficulty corrects itself (directly related to the problem being discussed) or due to reconnects (i.e. if you lose pool connection)

The fix for the 2nd one (reconnects) is simply an enhancement ... that no doubt there will be few arguments about (when it gets in vogue Tongue) since it is just an enhancement - no compatibility issue with the current implementation.
Ya my first several shares are usually rejects. I am mining over wifi, with about a dozen+ other computers on the network, so DCs are a fact of life. Still, I can live with 0.3% for now. Wink

LOL @ WIFI

Donations welcome: 12KaKtrK52iQjPdtsJq7fJ7smC32tXWbWr
crazyates
Legendary
*
Offline Offline

Activity: 938



View Profile
November 27, 2012, 04:31:58 AM
 #8257

Ya my first several shares are usually rejects. I am mining over wifi, with about a dozen+ other computers on the network, so DCs are a fact of life. Still, I can live with 0.3% for now. Wink
Don't go further. This is the issue.
I'm not complaining. I know it's a problem, but one I sorta have to live with. Tongue

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
optimator
Sr. Member
****
Offline Offline

Activity: 351



View Profile WWW
November 27, 2012, 07:10:30 AM
 #8258

Stratum jobs can be used infinitely, until the block is invalid or the pool expires the job. Unlike getwork, there is no 232 nonce limit.

True. But there is a limit to ntime. If a pool were to hash a stratum job ad nauseam and finally solve it, and then submit it, it would be rejected based on ntime (being some large time into the future). Stratum doesn't roll ntime and thus depends on the pool pushing new work requests.

kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
November 27, 2012, 07:28:04 AM
 #8259

Ya my first several shares are usually rejects. I am mining over wifi, with about a dozen+ other computers on the network, so DCs are a fact of life. Still, I can live with 0.3% for now. Wink
Don't go further. This is the issue.
I'm not complaining. I know it's a problem, but one I sorta have to live with. Tongue
... only until the current stratum problem is resolved and we move on to 'discussing' the reconnect issue and fixing that Smiley

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
November 27, 2012, 09:53:28 AM
 #8260

Perhaps slush could clarify the current meaning

I don't understand what is unclear here.

a) clean_jobs=False means that previous jobs are still valid.
b) clean_jobs=True means that previous jobs become invalid.
c) If new work is received, miner automatically should use this job. There's no reason why to add a new flag to specify this, it is "by default". However miners can do whatever they want, because with or without a special flag, previous jobs are still valid.

KISS, please.

Pages: « 1 ... 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 [413] 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 ... 830 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!