Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 199. (Read 409641 times)

I made 998 threads on several machines with Xeon processors (2 cpus), now waiting for block 512 threads gave me near 200.000KH performance, but I'm not sure that it is 'real' number showing in benchmark. Anyway, with such speed I should get blocks up to 10 times more often, if so - I'll confirm

lol not sure if it is a bug but I did increase the i7 threads to 880 and getting about 298763 khash/s but machine is almost unusable 

There is minerd thread limit 999  So I added 998 threads to my machines , I'll report if it gives real block generation speed increase

yeah maybe even GH/s with GPU but I have not ported to opencl yet but plan is to get that done before xmas

throughput wise with the sphlib

sha256 ~ 277MB/s
blake256 ~ 400MB/s

You should be well into the triple or quadruple digit MH/s with a GPU

BLAKE has higher throughput than SHA256 if I'm remembering correctly

I don't see why not try mining with it and if you get accepted blocks it works, tried on my Intel i7 2600k machine but not getting much speed increase are you both using Amd based hardware?

just tested on a old core2 e7300 and I can confirm speed increase with 256 threads

I confirm that - increasing number of threads increases speed (is benchmark correct in such case? )
I set thread number to 256 (24-core processor), and got 66613 KH (comparing to 17000 KH with default numbers)

I use Windows 8 pro 64 bit.
I made ​​a start.bat file with this command
start minerd -o 127.0.0.1:8772 -O u:p -a blake -s 2 --no-longpoll --no-stratum -t 128
default is 8 threads for my CPU, but I increased (8, 16, 32 ...) to test how much I can load my CPU just for fun and unexpectedly I got very strange good results  
my CPU can handle up to 200 threads but after a few seconds everything freezes and I have to restart my computer.
I found that the best performance are between 100-150 threads for my CPU.
Yes, 128 threads are crazy but minerd works perfectly and I can use the rest part of the computer for surfing, watching movies, etc.

 

very nice what is the command you are using in console?

benchmark

I have not changed anything except that I added a little more threads with "-t" option, I use the original minerd from 1st post.
I'm surprised I did not expect such a result 

have you made any changes to the miner?
what os are you running and did you compile from source or prebuild?

if you can confirm with benchmark I will add as fastest miner so far 

can you run minerd with benchmark option? (see first post)

It's that normal speed with AMD FX-8150?

In the first post I see examples of CPU speed, but that speed is 7-8 times faster.

New version released please upgrade or rebuild your wallets

• fixed some bugs
• added more checkpoints
• tweaked the limit up(takes effect block 3500 onwards)

any other bugs please report them asap

that's good news kramble I will look into midstate optimisation today

A question on the difficulty ...

pi@tvpi ~/blakecoin $ ./blakecoind getblockhash 0
000000ba5cae4648b1a2b823f84cc3424e5d96d7234b39c6bb42800b2c7639be
pi@tvpi ~/blakecoin $ ./blakecoind getblockhash 100
0000007dbd60e1d087628c768e97db480fcb2f3c2698e8994cb714a0fdd84fba
pi@tvpi ~/blakecoin $ ./blakecoind getblockhash 1000
0000000367d9064a7e537994e6808645d5877aadb84cb01ecd3a0678537e6827
pi@tvpi ~/blakecoin $ ./blakecoind getblockhash 2500
00000000041a372adf4c7bf72cf82e4c47a8e101e11d98d0677c8f73c4cb9c9e
pi@tvpi ~/blakecoin $

These blocks report difficulty as 1.0 (genesis block), 2.0 (block 100), 74 (block 1000) and 6668 (block 2500).
But the hashes for the first two are only prefixed "000000" rather than the "00000000" for bitcoin or "0000" for litecoin, so I guess the reference target for diff=1 is something like 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffff000000 ? Perhaps this goes some way to explaining the rapid difficulty increase?

Anyway in other news I've made a start on the FPGA miner. Not got it running yet, but its already apparent that the midstate optimisation applies to the blake algorithm. This should also work for the CPU/GPU mining code (I don't see it in the current cpuminer, so that's an easy 100% performance boost for anyone who wants to give it a try).

1000BLC=1btc

or

1000BLC=250XPM

anyone want to exchange?

Is this a bug or what, that i have to restart blakecoin wallet few times a day, or else i mine blocks that are generated but not accepted....

I have 12 blocks in 30 hours on Core i 7 3820.
10600 Kh\s.

restart your wallet if it gets stuck?

Blakecoin works?
I'm stuck on block 2198

21:32:09
{
"blocks" : 2198,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 7435.54002818,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}

00:12:56
{
"blocks" : 2198,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 7435.54002818,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}