 Show Posts
|
|
Pages: [1]
|
I can't find a mining calculator, so here's a fun experiment. I am mining BLC with a small R9 270 rig (4 cards), ~6.6 GH/s. For the past 6 days I had consistent mining (no disconnects / extended periods of not mining). I've graphed my results here:  Note: i just realized that's not an accurate BLC/day figure in the graph itself, I set the pool to pay out 50 BLC at a time and theres about 4 payouts per day so each mini bar is just a payout from the pool. I should update the label to not say blc/day (too lazy now that it's made).Anyways, according to the Bitcoin mining calculator with current BLC figures, I'm supposed to mine 283.3909 BLC/day. If you factor in that BLC is 30% more efficient than bitcoin: 283.4 - (283.4 * 0.30) = 198.38 -- very close to my observed ~200 BLC/day. Is there a mining calculator out there I just don't know about? Also, is there any p2pool setup yet? The network seems very centralized on blakecoin.org servers at the moment. EDITOkay, fixed the graph:  |
|
|
|
yes please, share your .config or .bat setting
Sure thing - I use this same config (but scrypt instead of blake256 algorithm, and "xintensity 4" with kalroth's miner) to mine scrypt at 500 KH/s stable, very good config. I am not undervolted, so I suspect that is what allows me to push the clock over 1150 and still be stable (this is how I achieve the high hash rates). "intensity" : "14",
"worksize" : "256",
"lookup-gap" : "2",
"gpu-threads" : "2",
"thread-concurrency" : "8193",
"gpu-engine" : "1165-1165",
"gpu-fan" : "0-100",
"gpu-memclock" : "1498",
"temp-cutoff" : "94",
"temp-overheat" : "88",
"temp-target" : "74",
"temp-hysteresis" : "3",
"api-mcast-port" : "4028",
"expiry" : "1",
"log" : "5",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "1",
"blake256" : true,
"kernel-path" : "/usr/local/bin",
"api-allow" : "W:127.0.0.1"
settings look good couple of things to point out "lookup-gap" : "2", not used by blake-256 kernel "thread-concurrency" : "8193", not used by blake-256 kernel "gpu-memclock" : "1498", blake does not use much ram so get the ram clocks lower(300-600) for better power usage and maybe a higher core clock "worksize" : "256", with newer ati drivers and latest 7 series or better (R9,R8,R7) cards try a odd worksize 255 reports of better share rate on pools WU/m (does not work for older 5/6 series) "scan-time" : "1", could reduce this and get less polling 30 for pools works well for me also note: "vectors" : "1", this is always 1 its due to the way kr105 has modded cgminer so just creates display bugs if you use anything but 1 Thank you for the input, I'll play with memclock and see if I can raise the core clock more. By the way, I'm trying to get a discussion going on reddit, I think BLC needs a subreddit and some marketing initiative to get the ball rolling on people adopting / learning about it. http://www.reddit.com/r/CryptoCurrency/comments/202169/discuss_blakecoin_blc_and_the_blake256_algorithm/ |
|
|
|
yes please, share your .config or .bat setting
Sure thing - I use this same config (but scrypt instead of blake256 algorithm, and "xintensity 4" with kalroth's miner) to mine scrypt at 500 KH/s stable, very good config. I am not undervolted, so I suspect that is what allows me to push the clock over 1150 and still be stable (this is how I achieve the high hash rates). "intensity" : "14",
"worksize" : "256",
"lookup-gap" : "2",
"gpu-threads" : "2",
"thread-concurrency" : "8193",
"gpu-engine" : "1165-1165",
"gpu-fan" : "0-100",
"gpu-memclock" : "1498",
"temp-cutoff" : "94",
"temp-overheat" : "88",
"temp-target" : "74",
"temp-hysteresis" : "3",
"api-mcast-port" : "4028",
"expiry" : "1",
"log" : "5",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "1",
"blake256" : true,
"kernel-path" : "/usr/local/bin",
"api-allow" : "W:127.0.0.1"
|
|
|
|
Last night I was enlightened by someone about Blakecoin and the future potential of the blake256 algorithm, so I've switched my mining rig to full time blc! Just wanted to report my hashrates for anybody with a similar setup looking for ball park numbers, I'm very impressed with the blake256 efficiency so far: high hash rates, low temps. I'm using the kR105 cgminer and running BAMT 1.5.2, it was actually quite easy to switch from scrypt to blake256 - I'm impressed. I have 4x Gigabyte R9 270s:  I'll be happy to share my config if anybody with 270s is interested, just ask. |
|
|
|
|
what architecture are the block erupters?
|
|
|
|
|
