Bitcoin Forum
June 27, 2024, 12:11:10 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Warning: One or more bitcointalk.org users have reported that they strongly believe that the creator of this topic is a scammer. (Login to see the detailed trust ratings.) While the bitcointalk.org administration does not verify such claims, you should proceed with extreme caution.
Pages: « 1 [2]  All
  Print  
Author Topic: Trying to move to eligius with Cointerra  (Read 1729 times)
kano
Legendary
*
Offline Offline

Activity: 4536
Merit: 1847


Linux since 1997 RedHat 4


View Profile
May 28, 2014, 02:26:42 AM
 #21

Let me just get the next few rounds of trolling out of the way...

*puts on best kano impersonation*

The work restart will make the empty blocks that your pool abuses the network with less likely to happen

*takes off kano hat* Not bad, eh?

But you still forget about the time the miner loses abandoning the old work, regardless of if it submits the already found results or not, it still takes an actual amount of time for the software and hardware to perform the full restart, which is lost time for the miner.  This is one of the reasons different types of hardware have widely varying results on fast-restart type situations like p2pool since a huge percentage of their time could be spent doing nothing useful do to the restarts.

If the restarts were seemless then there should never be a dip in shares submitted when a new network block is found and all miners should just smooth into it like nothing happened.  However, in reality, share submissions drop substantially at a full restart for some substantial amount of real time when it happens.

Heres some proof: Eligius block 301,134.  Found in 12 seconds after the previous block using the "empty" template work.  The pool wide hash rate average for the previous block: 5.8Ph/sec.  The pool-wide hash-rate for the 12 seconds between blocks: 4.1Ph.

This happens for every fast block.  A large percentage of miners haven't even caught up to the restart yet.  Just look at http://eligius.st/~wizkid057/newstats/blocks.php and look at the >9,000% luck blocks and the ones around them.  Its a recurring theme: miners do not quickly update work and lose real mining time for every restart.
Funny how I have to keep repeating myself ...

...
Coz there is ONLY an insignificant amount of time lost during a full work restart on most hardware.
Most hardware supports a work restart at any time.
Some limited amount of hardware does NOT support a work restart at any time - and that SAME hardware has the same problem every single block change since that of course requires a ...... full work restart ........................
...

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
Houseman
Member
**
Offline Offline

Activity: 156
Merit: 10


View Profile
May 28, 2014, 05:08:29 AM
 #22

Hi there,

Hoping someone can help.  I've been mining happily on ghash.io, I'm trying a move to eligius.st.

I've double checked all settings in the cointerra setup.  After restarting the CT with the new pool details saved, the hashrate starts at 1.6TH/s and very quickly slows to 200ghs and then goes onto stop.

I cannot see an option to change difficulty on eligius, is that because I'm a new user?

The config on the CT I am using is stratum+tcp://stratum.mining.eligius.st:3334 then my BTC address, then 1 for Priority and Qouta.

Any help appreciated.

David

"Happily mining ghash.io" so why change, sounds like a big headache now. Just put Eligius or whomever else as your fallback pool? Don't think any of us have answered your original question though  Wink

▮▮█ # metahashYour Gate to Decentralized Internet# metahash █▮▮
#TraceChain#MetaApps#MetaGate#MetaHashCoin
▮▮█▬▬▬▬▬❰Facebook❱▬❰Twitter❱▬❰Telegram❱▬❰Ann thread❱▬▬▬▬▬█▮▮
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!