Sk1llS
Member
 Offline
Activity: 87
Merit: 10
|
 |
February 18, 2014, 05:45:10 AM |
|
Not sure what you'd like me to tell you unfortunately... He looks to be a miner (multiple miners on one address), and is definitely making sure our servers can scale as far as we'd like them to. 1. How many is multiple miners? 1000 , 4000, 20000? 2. Are the hashrates for each miner similar? Or does each miner have a random/unique hashrate? Just trying to deduce if it's factory testing asics or a botnet. Makes my 13 Mh/s at WafflePool look small  |
|
|
|
|
|
|
|
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
ribaribigrizerep
Newbie
Offline
Activity: 1
Merit: 0
|
|
February 18, 2014, 06:10:40 AM |
|
8.18 Ghs. We'r growing bigger  |
|
|
|
|
dency45
Newbie
Offline
Activity: 42
Merit: 0
|
|
February 18, 2014, 06:18:51 AM |
|
What difficulty for my 900 hashrate? 8.18 Ghs. We'r growing bigger Many came from MC. lol |
|
|
|
|
eMiz0r
Member
Offline
Activity: 60
Merit: 10
|
|
February 18, 2014, 06:27:20 AM |
|
What difficulty for my 900 hashrate? 8.18 Ghs. We'r growing bigger Many came from MC. lol Wow true! MC is taking a serious hashratehit last 2 days. To be honest: I'm glad to see poolwaffle is now being payed for his hard work, transparancy and communication in this board. Switched over 2 weeks ago, and still happy about it |
|
|
|
|
|
poolwaffle (OP)
|
|
February 18, 2014, 09:07:43 AM |
|
So a quick status update for you guys. First off, pool is good and stable for the time being (hooray being able to handle an 8x pool expansion overnight!) Second thing, I've temporarily disabled coins with difficulty under 10 (even 10 may be a bit low). Essentially under this difficulty, we're fighting ourselves with orphans due to average block times, and network propagation rates (read: lower profitability). Our system does support mining multiple coins at once, but not at quite the fine-grained detail we would need to make these coins work, it was built to switch off like 25% of our hashrate to a coin, and leave the bulk on a larger coin, which was fine until now. Now however, 25% of our hashrate is still way too much to put on a single coin. So for the next couple days, while we get the switcher a bit more intelligent, we'll be mining some of the larger coins (10+ difficulty for now), which we'll lose out on a tiny bit of per-block profitability, but should win overall with the decrease in orphan blocks (read: higher profitability overall for now). Past the switcher upgrades, we've almost finished setting up another stratum endpoint (singapore), and will let you know when that is up And one last thing. I've noticed some dips in worker counts, and it looks like certain groups of workers will be connected for a while, suddenly drop, and reconnect a second later. I have some theories for what could cause this, but no hard data, as it is extremely difficulty to track down. If anyone is seeing a reasonably consistent (and ideally time-based) disconnect/reconnect pattern on their miner(s). Please email me ( poolwaffle@gmail.com) with your miner's IP address, and which endpoint you're connected to, it would help me to track it down if I can watch a few specific miners that are experiencing the issue. |
|
|
|
|
|
gaalx
|
|
February 18, 2014, 09:18:42 AM |
|
Question. When the password "x" floats complexity, probably it depends on the type of coins produced. On a farm in 2700 kH complexity can be from 64 to 512. Is this normal?
|
|
|
|
|
poolwaffle (OP)
|
|
February 18, 2014, 09:26:58 AM |
|
Question. When the password "x" floats complexity, probably it depends on the type of coins produced. On a farm in 2700 kH complexity can be from 64 to 512. Is this normal?
Should have nothing to do with coin being mined (or at least very little), only variance within the miner. For a 2.7MHs rig though, just set it to 512 or 1024 (either is fine) |
|
|
|
|
|
glon
|
|
February 18, 2014, 09:55:34 AM |
|
Question. When the password "x" floats complexity, probably it depends on the type of coins produced. On a farm in 2700 kH complexity can be from 64 to 512. Is this normal?
Should have nothing to do with coin being mined (or at least very little), only variance within the miner. For a 2.7MHs rig though, just set it to 512 or 1024 (either is fine) What if I have 4 different rigs, totalling 2.7Mhs, but one has 400MH, the other 700MH, etc, all pointing to the same BTC address? Should I just leave "x" in this case? |
|
|
|
|
|
gaalx
|
|
February 18, 2014, 10:01:41 AM |
|
Question. When the password "x" floats complexity, probably it depends on the type of coins produced. On a farm in 2700 kH complexity can be from 64 to 512. Is this normal?
Should have nothing to do with coin being mined (or at least very little), only variance within the miner. For a 2.7MHs rig though, just set it to 512 or 1024 (either is fine) left overnight (9-10 hours), one block (2700kH) with the "X" and the second 512. One where "x" Accept a 10% increase has turned out. although WU was greater in block 512. |
|
|
|
|
poolwaffle (OP)
|
|
February 18, 2014, 10:04:09 AM |
|
What if I have 4 different rigs, totalling 2.7Mhs, but one has 400MH, the other 700MH, etc, all pointing to the same BTC address? Should I just leave "x" in this case?
Overall you're better off setting a hardcoded difficulty. Lowers the work on the server overall, and if/when you disconnect, you don't start back from the default difficulty and ramp up. I'd personally use 64 for the 400MH, 128 for the 700MH, and 256 for anyhting around 1MH (512 above 1.5ish?). Theres no right answer, they'll all work fine, just a bit differently (more/less variance, more/less network connectivity, etc) |
|
|
|
|
dency45
Newbie
Offline
Activity: 42
Merit: 0
|
|
February 18, 2014, 10:25:44 AM |
|
What if I have 4 different rigs, totalling 2.7Mhs, but one has 400MH, the other 700MH, etc, all pointing to the same BTC address? Should I just leave "x" in this case?
Overall you're better off setting a hardcoded difficulty. Lowers the work on the server overall, and if/when you disconnect, you don't start back from the default difficulty and ramp up. I'd personally use 64 for the 400MH, 128 for the 700MH, and 256 for anyhting around 1MH (512 above 1.5ish?). Theres no right answer, they'll all work fine, just a bit differently (more/less variance, more/less network connectivity, etc) Do you mean 400KH and 700KH? |
|
|
|
|
Sk1llS
Member
Offline
Activity: 87
Merit: 10
|
|
February 18, 2014, 10:27:07 AM |
|
Not sure what you'd like me to tell you unfortunately... He looks to be a miner (multiple miners on one address), and is definitely making sure our servers can scale as far as we'd like them to. 1. How many is multiple miners? 1000 , 4000, 20000? 2. Are the hashrates for each miner similar? Or does each miner have a random/unique hashrate? Just trying to deduce if it's factory testing asics or a botnet. Makes my 13 Mh/s at WafflePool look small @PoolWaffle 3. Also are the IP's of the miners random or coming from the same block? |
|
|
|
|
|
oktay50000
|
|
February 18, 2014, 10:59:02 AM |
|
|
BTC : bc1qqz9hvv806w2zs42mx4rn576whxmr202yxp00e9
feel free to buy me a bear
|
|
|
|
glon
|
|
February 18, 2014, 10:59:37 AM |
|
What if I have 4 different rigs, totalling 2.7Mhs, but one has 400MH, the other 700MH, etc, all pointing to the same BTC address? Should I just leave "x" in this case?
Overall you're better off setting a hardcoded difficulty. Lowers the work on the server overall, and if/when you disconnect, you don't start back from the default difficulty and ramp up. I'd personally use 64 for the 400MH, 128 for the 700MH, and 256 for anyhting around 1MH (512 above 1.5ish?). Theres no right answer, they'll all work fine, just a bit differently (more/less variance, more/less network connectivity, etc) Do you mean 400KH and 700KH? Yeah I made a mistake there and meant KH so I'm wondering if poolwaffle did mean KH as well? |
|
|
|
|
dansky
Newbie
Offline
Activity: 13
Merit: 0
|
|
February 18, 2014, 11:03:48 AM |
|
Think we're getting DOS'd or something, my miner dropped to 28 kh/s from 1.4 mh/s and the pool to 200 mh/s
EDIT: looks like its ramping back up
|
|
|
|
|
|
oktay50000
|
|
February 18, 2014, 11:06:48 AM |
|
Think we're getting DOS'd or something, my miner dropped to 28 kh/s from 1.4 mh/s and the pool to 200 mh/s
my hashrate droped too...  pool hash droped fomr 8gh ro 3.7gh  |
BTC : bc1qqz9hvv806w2zs42mx4rn576whxmr202yxp00e9
feel free to buy me a bear
|
|
|
|
poolwaffle (OP)
|
|
February 18, 2014, 11:10:29 AM |
|
Think we're getting DOS'd or something, my miner dropped to 28 kh/s from 1.4 mh/s and the pool to 200 mh/s
my hashrate droped too... pool hash droped fomr 8gh ro 3.7gh Yep, we needed to restart the endpoints to get some new code in there. Should fix problems for people who were having disconnect/reconnect issues, but took a few minutes of downtime, so during that time the pool hashrate plummeted (its over the last 5 minutes), and should now be sliding back up to normal |
|
|
|
|
dansky
Newbie
Offline
Activity: 13
Merit: 0
|
|
February 18, 2014, 11:13:40 AM |
|
Yep, we needed to restart the endpoints to get some new code in there. Should fix problems for people who were having disconnect/reconnect issues, but took a few minutes of downtime, so during that time the pool hashrate plummeted (its over the last 5 minutes), and should now be sliding back up to normal Thanks for the excellent communication  |
|
|
|
|
|
oktay50000
|
|
February 18, 2014, 11:15:41 AM |
|
yup back to normal...
thanks for great support
|
BTC : bc1qqz9hvv806w2zs42mx4rn576whxmr202yxp00e9
feel free to buy me a bear
|
|
|
coyote
Newbie
Offline
Activity: 58
Merit: 0
|
|
February 18, 2014, 11:19:32 AM |
|
Think we're getting DOS'd or something, my miner dropped to 28 kh/s from 1.4 mh/s and the pool to 200 mh/s
my hashrate droped too... pool hash droped fomr 8gh ro 3.7gh Yep, we needed to restart the endpoints to get some new code in there. Should fix problems for people who were having disconnect/reconnect issues, but took a few minutes of downtime, so during that time the pool hashrate plummeted (its over the last 5 minutes), and should now be sliding back up to normal Hi Poolwaffle when doing maintenance on an endpoint could you take it completely offline? That way our rigs can failover to another endpoint. Thanks |
|
|
|
|
|
