Bitcoin Forum
December 10, 2016, 07:08:04 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 [157] 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 »
  Print  
Author Topic: bitHopper: Python Pool Hopper Proxy  (Read 333147 times)
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1960


Poor impulse control.


View Profile WWW
August 09, 2011, 02:02:08 AM
 #3121

@joulesbeef: ok, if you're going to use extremes of pool speed or hashrate , sure. Variance will kill you and long term becomes months rather than weeks or days. But then over the *very* long term, oDS will still win over slice.

Choosing larger pools (~50Ghps and above) is a simpler and more efficient was of reducing variance. Yes - the more pools the better - but the efficiency loss due to having to use slice to reduce variance might be an issue.

Edit: Also don't forget you wouldn't have only been mining on bloody's the whole time, only when it had fewer total shares than any other pool. Mining on a small pool is risky, so your  is to increase risk to get more pools and possibly a better payout. But because of the increased risk you need slicing to reduce variance, which also reduces payout.

Quote
I'd like to see some more graphs and math before i am sold.

and I'd like to make some chartporn for you (you know you want it...) but I really don't know how to model slice until until someone explains exactly how it works inmining on a small pool all circumstances. PM me if you have something I can use (ie a decision tree, flowchart or some other human language algo) and not just the actual code.


Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
1481353684
Hero Member
*
Offline Offline

Posts: 1481353684

View Profile Personal Message (Offline)

Ignore
1481353684
Reply with quote  #2

1481353684
Report to moderator
1481353684
Hero Member
*
Offline Offline

Posts: 1481353684

View Profile Personal Message (Offline)

Ignore
1481353684
Reply with quote  #2

1481353684
Report to moderator
1481353684
Hero Member
*
Offline Offline

Posts: 1481353684

View Profile Personal Message (Offline)

Ignore
1481353684
Reply with quote  #2

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

Posts: 1481353684

View Profile Personal Message (Offline)

Ignore
1481353684
Reply with quote  #2

1481353684
Report to moderator
simonk83
Hero Member
*****
Offline Offline

Activity: 896


View Profile
August 09, 2011, 02:16:47 AM
 #3122

Oops, just saw loads (more than I manage to capture) of this as my miners went idle:

Code:
[12:15:11] RPC request [getwork] submitted to PolMine.pl
[12:15:11] RPC request [getwork] submitted to PolMine.pl
[12:15:11] RPC request [getwork] submitted to PolMine.pl
[12:15:11] RPC request [getwork] submitted to PolMine.pl
[12:15:12] RPC request [getwork] submitted to PolMine.pl
[12:15:12] RPC request [getwork] submitted to PolMine.pl
[12:15:13] RPC request [getwork] submitted to PolMine.pl
[12:15:13] RPC request [getwork] submitted to PolMine.pl
[12:15:14] RPC request [getwork] submitted to PolMine.pl
[12:15:14] RPC request [getwork] submitted to PolMine.pl
[12:15:15] RPC request [getwork] submitted to PolMine.pl
[12:15:15] RPC request [getwork] submitted to PolMine.pl
[12:15:15] triple: 858469
[12:15:15] RPC request [getwork] submitted to PolMine.pl
[12:15:15] RPC request [getwork] submitted to PolMine.pl
[12:15:16] RPC request [getwork] submitted to PolMine.pl
[12:15:16] RPC request [getwork] submitted to PolMine.pl
[12:15:17] RPC request [getwork] submitted to PolMine.pl
[12:15:17] RPC request [getwork] submitted to PolMine.pl
[12:15:18] RPC request [getwork] submitted to PolMine.pl
[12:15:18] RPC request [getwork] submitted to PolMine.pl
[12:15:19] RPC request [getwork] submitted to PolMine.pl
[12:15:19] RPC request [getwork] submitted to PolMine.pl
[12:15:19] RPC request [getwork] submitted to PolMine.pl
[12:15:19] RPC request [getwork] submitted to PolMine.pl
[12:15:20] RPC request [getwork] submitted to PolMine.pl
[12:15:20] RPC request [getwork] submitted to PolMine.pl
[12:15:21] RPC request [getwork] submitted to PolMine.pl
[12:15:21] RPC request [getwork] submitted to PolMine.pl
[12:15:21] slush: 2500803
[12:15:22] RPC request [getwork] submitted to PolMine.pl
[12:15:22] RPC request [getwork] submitted to PolMine.pl
[12:15:23] RPC request [getwork] submitted to PolMine.pl
[12:15:23] RPC request [getwork] submitted to PolMine.pl
[12:15:23] RPC request [getwork] submitted to PolMine.pl
[12:15:23] RPC request [getwork] submitted to PolMine.pl
[12:15:24] mtred: 264683
[12:15:25] Error in pool api for itzod
[12:15:25] RPC request [getwork] submitted to PolMine.pl
[12:15:25] RPC request [getwork] submitted to PolMine.pl
[12:15:26] RPC request [getwork] submitted to PolMine.pl
[12:15:26] RPC request [getwork] submitted to PolMine.pl
[12:15:27] RPC request [getwork] submitted to PolMine.pl
[12:15:27] RPC request [getwork] submitted to PolMine.pl
[12:15:28] RPC request [getwork] submitted to PolMine.pl
[12:15:28] RPC request [getwork] submitted to PolMine.pl
[12:15:28] RPC request [getwork] submitted to PolMine.pl
[12:15:28] RPC request [getwork] submitted to PolMine.pl
[12:15:29] RPC request [getwork] submitted to PolMine.pl
[12:15:29] RPC request [getwork] submitted to PolMine.pl
[12:15:30] RPC request [getwork] submitted to PolMine.pl
[12:15:30] RPC request [getwork] submitted to PolMine.pl
[12:15:31] RPC request [getwork] submitted to PolMine.pl
[12:15:31] RPC request [getwork] submitted to PolMine.pl
[12:15:32] RPC request [getwork] submitted to PolMine.pl
[12:15:32] RPC request [getwork] submitted to PolMine.pl
[12:15:32] Server change to mtred

Followed straight after by:

Code:
[12:16:14] RPC request [getwork] submitted to BTCServ.net
[12:16:16] RPC request [04130000] submitted to OzCo.in
[12:16:20] RPC request [getwork] submitted to BTCServ.net
[12:16:21] RPC request [getwork] submitted to BTCServ.net
[12:16:22] RPC request [getwork] submitted to BTCServ.net
[12:16:22] RPC request [0d9c5000] submitted to OzCo.in
[12:16:22] triple: 859632
[12:16:22] bitp: 1214343
[12:16:22] RPC request [getwork] submitted to BTCServ.net
[12:16:23] RPC request [getwork] submitted to BTCServ.net
[12:16:23] RPC request [getwork] submitted to BTCServ.net
[12:16:24] RPC request [getwork] submitted to BTCServ.net
[12:16:24] RPC request [getwork] submitted to BTCServ.net
[12:16:24] bcpool: 2539522
[12:16:24] RPC request [getwork] submitted to BTCServ.net
[12:16:25] RPC request [getwork] submitted to BTCServ.net
[12:16:25] RPC request [getwork] submitted to BTCServ.net
[12:16:25] RPC request [getwork] submitted to BTCServ.net
[12:16:26] slush: 2525203
[12:16:26] RPC request [getwork] submitted to BTCServ.net
[12:16:26] RPC request [getwork] submitted to BTCServ.net
[12:16:27] RPC request [getwork] submitted to BTCServ.net
[12:16:27] RPC request [getwork] submitted to BTCServ.net
[12:16:27] RPC request [getwork] submitted to BTCServ.net
[12:16:27] RPC request [getwork] submitted to BTCServ.net
[12:16:28] Error in pool api for itzod
[12:16:28] RPC request [getwork] submitted to BTCServ.net
[12:16:28] RPC request [getwork] submitted to BTCServ.net
[12:16:29] RPC request [getwork] submitted to BTCServ.net
[12:16:29] RPC request [getwork] submitted to BTCServ.net
[12:16:30] RPC request [getwork] submitted to BTCServ.net
[12:16:30] RPC request [getwork] submitted to BTCServ.net
[12:16:30] RPC request [getwork] submitted to BTCServ.net
[12:16:30] RPC request [getwork] submitted to BTCServ.net
[12:16:31] RPC request [getwork] submitted to BTCServ.net
[12:16:31] RPC request [getwork] submitted to BTCServ.net
[12:16:32] RPC request [getwork] submitted to BTCServ.net
[12:16:32] RPC request [getwork] submitted to BTCServ.net
[12:16:33] RPC request [getwork] submitted to BTCServ.net
[12:16:33] RPC request [getwork] submitted to BTCServ.net
[12:16:33] RPC request [getwork] submitted to BTCServ.net
[12:16:33] RPC request [getwork] submitted to BTCServ.net
[12:16:34] RPC request [getwork] submitted to BTCServ.net
[12:16:34] RPC request [getwork] submitted to BTCServ.net
[12:16:35] RPC request [getwork] submitted to BTCServ.net
[12:16:35] RPC request [getwork] submitted to BTCServ.net
[12:16:36] RPC request [getwork] submitted to BTCServ.net
[12:16:36] RPC request [getwork] submitted to BTCServ.net
[12:16:36] RPC request [getwork] submitted to BTCServ.net
[12:16:36] RPC request [getwork] submitted to BTCServ.net
[12:16:37] RPC request [getwork] submitted to BTCServ.net
[12:16:37] RPC request [getwork] submitted to BTCServ.net
[12:16:38] RPC request [getwork] submitted to BTCServ.net
[12:16:38] RPC request [getwork] submitted to BTCServ.net
[12:16:38] btcserv: 120273
[12:16:39] RPC request [getwork] submitted to BTCServ.net
[12:16:39] RPC request [getwork] submitted to BTCServ.net
[12:16:39] RPC request [getwork] submitted to BTCServ.net
[12:16:39] RPC request [getwork] submitted to BTCServ.net
[12:16:40] RPC request [getwork] submitted to BTCServ.net
[12:16:40] RPC request [getwork] submitted to BTCServ.net
[12:16:40] btcmonkey: 3516104
[12:16:41] RPC request [getwork] submitted to BTCServ.net
[12:16:41] RPC request [getwork] submitted to BTCServ.net
[12:16:42] RPC request [getwork] submitted to BTCServ.net
[12:16:42] RPC request [getwork] submitted to BTCServ.net
bb
Member
**
Offline Offline

Activity: 84


View Profile
August 09, 2011, 02:21:05 AM
 #3123

Hope everybody was on MtRed.  Grin

Same goes for ozcoin I guess. Smiley

Btw, do we actually know if the 10% slush mining will work out?
paraipan
Legendary
*
Offline Offline

Activity: 924


Firstbits: 1pirata


View Profile WWW
August 09, 2011, 02:26:30 AM
 #3124

@simonk83 happened to me a moment ago with mt.red , just deleted the log thinking it's a connection prob with them, seems like it happens with a server it chosen by bH, please run it with
Code:
--debug > output.log
if you dont mind

BTCitcoin: An Idea Worth Saving - Q&A with bitcoins on rugatu.com - Check my rep
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 09, 2011, 02:29:12 AM
 #3125

Um, I just redid the whole deepbit system again to produce estimated share counts. So every scheduler now works!

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
simonk83
Hero Member
*****
Offline Offline

Activity: 896


View Profile
August 09, 2011, 02:32:37 AM
 #3126

@simonk83 happened to me a moment ago with mt.red , just deleted the log thinking it's a connection prob with them, seems like it happens with a server it chosen by bH, please run it with
Code:
--debug > output.log
if you dont mind

I realised I wasn't quite on the latest, so I've done a pull.  If it happens again I'll run it via debug and grab the log.  Seems OK for now though (although it was running for a few hours prior to those errors happening).
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476


moOo


View Profile
August 09, 2011, 02:38:03 AM
 #3127

Um, I just redid the whole deepbit system again to produce estimated share counts. So every scheduler now works!

kick butt c00w


and i just submitted my first deepbit share.. WOOHOO
lol
one the one so far Sad

but I havent upgraded yet. i'm on 1.3-63

mooo for rent
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476


moOo


View Profile
August 09, 2011, 02:48:08 AM
 #3128

Ok who erased OldDefaultScheduler from the wiki?

it's a valid scheduler..which some think might be the best one there is. Just cause it is called old, no need to erase it from existence.



mooo for rent
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 09, 2011, 02:50:31 AM
 #3129

Wiki history shows who did what. I'll track em down Tongue

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
paraipan
Legendary
*
Offline Offline

Activity: 924


Firstbits: 1pirata


View Profile WWW
August 09, 2011, 02:54:49 AM
 #3130

Ok who erased OldDefaultScheduler from the wiki?

it's a valid scheduler..which some think might be the best one there is. Just cause it is called old, no need to erase it from existence.




me did it  Sad, sorry

BTCitcoin: An Idea Worth Saving - Q&A with bitcoins on rugatu.com - Check my rep
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476


moOo


View Profile
August 09, 2011, 02:55:18 AM
 #3131

It was paraipanakos!! I knew it! He always had it in for OldDefaultScheduler.

You should code into the next hopper, If user = paraipanakos then mine+charity everything  Tongue

mooo for rent
GenTarkin
Legendary
*
Offline Offline

Activity: 1932


View Profile
August 09, 2011, 02:56:35 AM
 #3132

LOL! So, question what exactly is the diff between the old default scheduler and the new one. I notice the old one doesnt list the "slice" column...

GenTarkin's MOD Kncminer Titan custom firmware! v1.0.4! <--- CLICK HERE
Donations: bitcoin- 1Px71mWNQNKW19xuARqrmnbcem1dXqJ3At || litecoin- LYXrLis3ik6TRn8tdvzAyJ264DRvwYVeEw
paraipan
Legendary
*
Offline Offline

Activity: 924


Firstbits: 1pirata


View Profile WWW
August 09, 2011, 02:58:16 AM
 #3133

It was paraipanakos!! I knew it! He always had it in for OldDefaultScheduler.

You should code into the next hopper, If user = paraipanakos then mine+charity everything  Tongue

 Cheesy nice, I was asking for it

edit: (mental note) don't mess with things I can't remember what are used for

BTCitcoin: An Idea Worth Saving - Q&A with bitcoins on rugatu.com - Check my rep
djex
Full Member
***
Offline Offline

Activity: 196


View Profile
August 09, 2011, 02:58:36 AM
 #3134

Ok who erased OldDefaultScheduler from the wiki?

it's a valid scheduler..which some think might be the best one there is. Just cause it is called old, no need to erase it from existence.

IMO best one regards to payout. I found with slicing my payout is often below the daily expected payout for my hash rate but with the OldDefaultScheduler payout is around 0.28 BTC more than the expected.

Smiley  : 1LbvSEJwtQZKLSQQVYxQJes8YneQk2yhE3
bb
Member
**
Offline Offline

Activity: 84


View Profile
August 09, 2011, 03:06:13 AM
 #3135

@GenTarkin: old one doesn't slice, it just (more or less) stays at the pool with the lowest share count.

@djex: slicing has only been around for so long. Give it some time to kill the variance. Smiley
djex
Full Member
***
Offline Offline

Activity: 196


View Profile
August 09, 2011, 03:11:08 AM
 #3136

So with mine_deepbit I should switch to info on all possible pools (out of the ones disabled) that will give proper stats?

Smiley  : 1LbvSEJwtQZKLSQQVYxQJes8YneQk2yhE3
muyoso
Member
**
Offline Offline

Activity: 84



View Profile
August 09, 2011, 03:13:00 AM
 #3137

Can't wait to hear the first reports back on the deepbit hopping.  Been excited ever since I read about it yesterday.  

I drink it up!
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476


moOo


View Profile
August 09, 2011, 03:13:21 AM
 #3138

LOL! So, question what exactly is the diff between the old default scheduler and the new one. I notice the old one doesnt list the "slice" column...


see this discussion here


i'm giving him a hard time with extremes, but there is a lot of evidence to support him that it is the best scheduler

I'm not 100% sold due to some slow pools, but I'm running it now. Have to give due warning about the stats page.. it's different

which brings up.. who is most responsible for the altslicescheduler?

I just have some questions on how it works, for organofcorti to sim.
Quote
So with mine_deepbit I should switch to info on all possible pools (out of the ones disabled) that will give proper stats?

yes
i add BTCmine as well.. it was never hoppable but it is one of the ten largest pools.
not sure if it is in the hopper.

mooo for rent
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 09, 2011, 03:14:32 AM
 #3139

@djex

Um we actually don't use the other servers in the latest iteration. We probably should. But our cutoff times are a lot better.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 09, 2011, 03:16:18 AM
 #3140

I recon there is an extra method to "slicing" that wasnt considered here yet.

Adjusting mining method based on time left till next difficulty and considering current difficulty to next difficulty increase/decrease.

If next difficulty is soon (insert random low timeframe) and difficulty is increasing (insert random increase percentage here) then stick to (insert random fast pools with lower share)
If next difficulty is soon (insert random low timeframe) and difficulty is decreasing (insert random decrease percentage here) then ignore (insert random pool speed and only consider lowest share)

If next difficulty is in a while (insert random high timeframe) and difficulty is increasing (insert random increase percentage here) then ignore (insert random pool speed and only consider min shares)


I think you could even narrow the timeframes down with some neat formula considering pool avg daily hashrate , share count , next difficulty(up or down) and lastly timeframe till next difficulty adjustment.

Its important to consider difficulty adjustments when mining low share slow pools since they can easily spread across difficulties where you will get penalised even more.

This approach should make the whole lowest shares vs fastest pool debate move more smoothly.


...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
Pages: « 1 ... 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 [157] 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 »
  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!