|
These are my most recent deepbit stats:
Block Shares
Time/Link Found in Your Total Reward
09.08 10:19:29 0h 03m 25 270595 0.00448087
09.08 10:15:55 0h 01m 7 125063 0.00271463
09.08 10:14:11 0h 07m 0 608030 None
09.08 10:06:16 0h 44m 76 3392096 0.00108664
09.08 09:21:52 0h 20m 0 1586080 None
Oh, and it seems because deepbit doesnt use slicing method on default slicer... Because of this the fresh block on slush was skipped entirely... =/ I dont know if this is the desired behaviour, just some feedback!
|
|
|
|
Deepbit:
09.08 18:21:52 0h 20m 203 1586080 0.00620744
That's for 2950Mhash/s, Default scheduler and threshold at 60% (.6)
hrm....WTF?!?!? my stats on deepbit say 000 shares for me on that exact round! Although, I know I hopped over to deepbit more than an hour ago. I am just using default scheduler, default threshold. Deepbit was confirming I submitted shares during that time period ( I watched my worker on their site) I mine at about 366mh/s ideas? EDIT: couple mins later, just saw another LP hit and went over to deepbit...mining there again. Is there a bug thats causing deepbit to get mined on every LP? ... it seems thats the behaviour even when the LP says someone else owns the block. |
|
|
|
|
k, Ill go back to standard...I will just use --startLP
|
|
|
|
I do think we need to put the threshold to 100%
I do think organofcorti was right on that.
but a little over 100% and your shares become cheaper than pps.
I don't want such a big step at once, so I try at 60% for 3 days and see what it does  One advantage is that it (almost) never needs a backup pool at that setting. So, you mean you set penalty to .6 for deepbit? |
|
|
|
Well, it just hopped off deepbit and back over to mtred
well it's supposed to do that, at what threshold (diff. level) Think it was right around the 43% or 50% reported by stats for deepbit...if they are accurate, not sure. So, are those shares being estimated based on when a longpoll detects a block from them and their given hashrate, to figure out where they are in a current round? I was on default scheduler as well =) |
|
|
|
|
Well, it just hopped off deepbit and back over to mtred
|
|
|
|
|
Im mining on deepbit as well...so heres a question, how does it determine when to hop off deepbit? Since its stats are delayed we cant exactly rely on 43% can we?
|
|
|
|
|
Ive been running latest build w/ --startLP and mine_deepbit on deepbit and it hasnt put one share on deepbit at all =(
|
|
|
|
|
So, I just saw a bunch of new blocks pop up like 2 or 3 ... but, BH said they were owned by 2 diff pools in the LP output....but those 2 pools on the stats page did not get their shares reset... Im confused...shouldnt the shares reset if they found new blocks? (if the LP implementation is working properly in BH?)
|
|
|
|
|
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...
|
|
|
|
slush just got a new block and the hopper didnt switch over to it, its still making sure the other hoppable pools slice accounts are "caught up" =(... I want slush to take priority over those...grr
Pull the latest code from c00w. There is code now to jump to slush while it's "hot" and return to normal when it's not, but only with the alternate scheduler: --scheduler=AltSliceScheduler and only when it's set to mine_slush. Isn't this possible to do with the default slicer? It will mine ONLY on slush, until approximately 10% is reached. Yeah, Id like some clarification on this, because I jsut sat here and watched the default scheduler just keep switching between 3 pools when slush's was around 2% till 11%.... =( I hope you can see the clarification. he was only working on that one scheduler, so no, it isnt on the default... not to be overly snarky HAHA, well call me blind =P Thanks for the clarification and yes! I want this on the default scheduler as well so I can use it along w/ testing deepbit startLP mining.... |
|
|
|
slush just got a new block and the hopper didnt switch over to it, its still making sure the other hoppable pools slice accounts are "caught up" =(... I want slush to take priority over those...grr
Pull the latest code from c00w. There is code now to jump to slush while it's "hot" and return to normal when it's not, but only with the alternate scheduler: --scheduler=AltSliceScheduler and only when it's set to mine_slush. Isn't this possible to do with the default slicer? It will mine ONLY on slush, until approximately 10% is reached. Yeah, Id like some clarification on this, because I jsut sat here and watched the default scheduler just keep switching between 3 pools when slush's was around 2% till 11%.... =( |
|
|
|
|
slush just got a new block and the hopper didnt switch over to it, its still making sure the other hoppable pools slice accounts are "caught up" =(... I want slush to take priority over those...grr
|
|
|
|
|
Freakin awesome! And I just wanna say to the devels of this project... You guys FREAKIN ROCK!!! I see this becoming the end all be all to ultimate pool hopping! HAHA...
thanks again for all your hardwork....hope it lasts for quite some time!
Wish I knew how to program worth a damn...
Oh, while Im thinkin of it....is it best to hop the pools that have the higher gh/s rating, that way the hopper bounces around faster and it doesnt get stuck on a small pool tryin to do 43% for a long time?
|
|
|
|
|
I was wondering, since we stay on slush for such a small amount of time, shouldnt it be given priority over the other eligible pools for hopping? Because, I notice it stil switches back and forth between all hoppable pools when a slush round starts. I would like it to stay on slush till it goes over the 11% threshold...
Or is doing this not matter?
|
|
|
|
|
Bithopper is still crashing for me and then starts tons of spamming of text in the console, mining is inactive. =(
This happens after a few hours...
|
|
|
|
I think I fixed LP based hopping of deepbit. At the bare minimum I fixed a bunch of LP bugs. Um, it only works with the default scheduler for now. And it mines for the entire period of a block. So I'm not sure if its that great of a system.
Tried the most recent source build and ... get a lot of LP errors decoding in console...how do I copy and paste this stuff? I cant seem to do it while its running. Says "no JSON object could be decoded" |
|
|
|
|
c00w - does it matter what scheduler is used w/ --startLP & deepbit?
|
|
|
|
Um not really. Its better to set pools to info instead of disable as long as their API works so that we don't mine on deepbit when those servers find a block.
So, for all the backup pools I should make accounts and set them to just info? Does the more "info" specified pools help deepbit mining? Or at least make sure all the "bigger" pools have "info" on them? since they are more likely to find blocks then the tinier pools? |
|
|
|
|
Does the amount of pools I have set up / specified in user.cfg affect the way --startLP and deepbit mining works?
|
|
|
|
|
Show Posts
