Quote from: favdesu on November 09, 2013, 08:50:16 AM
It's 3 - 0 then

14 - 5 with ~9.5 hpm

So far the load on the pool server is essentially 0 and we are mining at a total of 105 connections... keep the hashes coming :)

From my side of things I am seeing very few stale nodes despite the fact that blocks keep coming at 30-40 second intervals..... I am sure this pool will not help with the hash rate growth!

Yes, I reset the server to remove some debug statements to reduce latency.

One of the biggest improvements in performance is rapid exit of the momentum search when a new block is found.  This has a bigger impact on slower machines.
Another improvement in performance came from having 8 threads work in parallel on the same search space.  This allowed me to search it faster and thus reduce latency further, it also reduced the memory footprint. 

he he  some fun error


End of file
    {"message":"End of file"}
    asio  asio.cpp:22 read_write_handler
attempting to connect to the-iland.net
206687ms th_a       miner.cpp:108                 main                 ] 64.90.183.137:8384
206825ms th_a       miner.cpp:114                 main                 ] unspecified
Broken pipe
    {"message":"Broken pipe"}
    asio  asio.cpp:28 read_write_handler
Unable to connect
attempting to connect to the-iland.net


Quote from: alexxy on November 09, 2013, 08:54:32 AM
release sources and someone will help you writing it

release sources and someone will help you writing it

Quote from: alexxy on November 09, 2013, 08:52:04 AM
Why you use hardcoded thread number? why not simply detect them on the fly like cpuminer did?

Because I wrote this in 24 hours and that required extra time I didn't have :)

I will make it auto detect soon.

Quote from: Brekyrself on November 09, 2013, 08:51:28 AM
Was getting ~17 with two instances on win64, now with the new miner ~30.  Nice job and quick action bytemaster.  I hope to see an all in one solution built into the qt client so I can easily get non tech friends to support the cause.

All-in-one miner will be included with Keyhotee when the time comes.

Why you use hardcoded thread number? why not simply detect them on the fly like cpuminer did?

Was getting ~17 with two instances on win64, now with the new miner ~30.  Nice job and quick action bytemaster.  I hope to see an all in one solution built into the qt client so I can easily get non tech friends to support the cause.

Quote from: bytemaster on November 09, 2013, 08:48:05 AM
I have a very low reject rate for my miners... what are you all seeing?   Remember to subtract 1 for each time you have started your client.

It's 3 - 0 then

pool-wide I am getting less than 7% reject rate right now and running at 56 shares per minute.

Quote from: favdesu on November 09, 2013, 08:45:02 AM

Quote from: bytemaster on November 09, 2013, 08:44:18 AM

Quote from: favdesu on November 09, 2013, 08:43:38 AM
3 hpm more than I get with other miners on win7

What is your base line?

6.5 now 8.5-9. keeping an eye on the rejection rate though

I have a very low reject rate for my miners... what are you all seeing?   Remember to subtract 1 for each time you have started your client.

Quote from: bytemaster on November 09, 2013, 08:44:18 AM

Quote from: favdesu on November 09, 2013, 08:43:38 AM
3 hpm more than I get with other miners on win7

What is your base line?

6.5 now 8.5-9. keeping an eye on the rejection rate though

Quote from: favdesu on November 09, 2013, 08:43:38 AM
3 hpm more than I get with other miners on win7

What is your base line?