[ANN] 1GH.COM - HVC / MAX / MMC / PTS / VIA Anonymous Pool ★

[Yanakitu Tenatako]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

[reorder]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

Please try using different XCN addresses as your workers usernames to get a lower difficulty. This coin updates blocks too often, a more frequent shares may give you better results.

[Yanakitu Tenatako]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

Please try using different XCN addresses as your workers usernames to get a lower difficulty. This coin updates blocks too often, a more frequent shares may give you better results.

Hmmm ok... will try...

[Yanakitu Tenatako]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

Please try using different XCN addresses as your workers usernames to get a lower difficulty. This coin updates blocks too often, a more frequent shares may give you better results.

Hmmm ok... will try...

I break it to 5 groups of 4 computers, with 4 different addresses. It DID NOT helped.
So, hashrate on pool is almos 1/2 of actual hashrate shown by minerd. WHY?

[reorder]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

Please try using different XCN addresses as your workers usernames to get a lower difficulty. This coin updates blocks too often, a more frequent shares may give you better results.

Hmmm ok... will try...

I break it to 5 groups of 4 computers, with 4 different addresses. It DID NOT helped.
So, hashrate on pool is almos 1/2 of actual hashrate shown by minerd. WHY?

Two possible reasons: statistical fluctuation (pool is averaging shares over 20 minute, so you have to wait at least that much to get realistic hashrate display), and some found shares not making it to the pool - this one could be caused by a high network latency or shares difficulty set too high. If you run a single worker on a single coin address over 20 minutes, does it still not match?

[Yanakitu Tenatako]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

Please try using different XCN addresses as your workers usernames to get a lower difficulty. This coin updates blocks too often, a more frequent shares may give you better results.

Hmmm ok... will try...

I break it to 5 groups of 4 computers, with 4 different addresses. It DID NOT helped.
So, hashrate on pool is almos 1/2 of actual hashrate shown by minerd. WHY?

Two possible reasons: statistical fluctuation (pool is averaging shares over 20 minute, so you have to wait at least that much to get realistic hashrate display), and some found shares not making it to the pool - this one could be caused by a high network latency or shares difficulty set too high. If you run a single worker on a single coin address over 20 minutes, does it still not match?

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay is that Boooo-s are 7,8%

[SRBOOTH]

Trying to compile 1GH cryptonite-cpuminer on ubuntu getting this error after ./configure CFLAGS="-O3" CXXFLAGS="-O3"

configure: error: GNU MP not found, see https://gmplib.org/

I may have a dependencies issue..........compile many miner in linux before but having problem with this one

Any help would be appreciated, I am weak at Linux..........Thanks

[reorder]

Trying to compile 1GH cryptonite-cpuminer on ubuntu getting this error after ./configure CFLAGS="-O3" CXXFLAGS="-O3"

configure: error: GNU MP not found, see https://gmplib.org/

I may have a dependencies issue..........compile many miner in linux before but having problem with this one

Any help would be appreciated, I am weak at Linux..........Thanks

'sudo apt-get install libgmp3-dev' might help.

[SRBOOTH]

Trying to compile 1GH cryptonite-cpuminer on ubuntu getting this error after ./configure CFLAGS="-O3" CXXFLAGS="-O3"

configure: error: GNU MP not found, see https://gmplib.org/

I may have a dependencies issue..........compile many miner in linux before but having problem with this one

Any help would be appreciated, I am weak at Linux..........Thanks

'sudo apt-get install libgmp3-dev' might help.

That was it ...thank you so much!!!

[reorder]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

Please try using different XCN addresses as your workers usernames to get a lower difficulty. This coin updates blocks too often, a more frequent shares may give you better results.

Hmmm ok... will try...

I break it to 5 groups of 4 computers, with 4 different addresses. It DID NOT helped.
So, hashrate on pool is almos 1/2 of actual hashrate shown by minerd. WHY?

Two possible reasons: statistical fluctuation (pool is averaging shares over 20 minute, so you have to wait at least that much to get realistic hashrate display), and some found shares not making it to the pool - this one could be caused by a high network latency or shares difficulty set too high. If you run a single worker on a single coin address over 20 minutes, does it still not match?

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay is that Boooo-s are 7,8%

There are also wild swings in total pool hashrate display, so probably we should be averaging more smoothly for display. However, the average total hashrate matches percentage of blocks found by the pool pretty closely, I believe it is 'just' a display issue or it may be worse for only some users. Would you please post or PM ping from one of your hosts to xcnpool.1gh.com?

We are also working on adding a stratum server for Asia-Pacific region so miners coming from there could get better lattencies and less stales. This is currently delayed somewhat by new version of wallet being still under development/bugfix.

[reorder]

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay is that Boooo-s are 7,8%

We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

[wayla]

I put 20 CPUs each of 340 khash speed, pool shows only half of that??? Last 2 hrs (since miner upgrade).

same issue

[wayla]

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay is that Boooo-s are 7,8%

We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

[reorder]

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay is that Boooo-s are 7,8%

We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

I have just rechecked:
[2014-08-04 05:06:58] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-04 05:06:58] 4 miner threads started, using 'm7' algorithm.
[2014-08-04 05:07:08] thread 1: 262144 hashes, 30.36 khash/s

It also only makes sense to use this server if you have better ping to it than to xcnpool.1gh.com

[alex666666]

who has some idea on this issue?

After LIBCURL="-lcurldll" ./configure CFLAGS="-O3"

checking gmp.h usability... yes
checking gmp.h presence... yes
checking for gmp.h... yes
./configure: line 5726: syntax error near unexpected token `,'
./configure: line 5726: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'

RHEL 6.5
-bash-4.1# uname -a
Linux 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

BTW,can 1gh provide a miner which compiled well on rhel 6.X ?

[reorder]

who has some idea on this issue?

After LIBCURL="-lcurldll" ./configure CFLAGS="-O3"

checking gmp.h usability... yes
checking gmp.h presence... yes
checking for gmp.h... yes
./configure: line 5726: syntax error near unexpected token `,'
./configure: line 5726: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'

RHEL 6.5
-bash-4.1# uname -a
Linux 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

BTW,can 1gh provide a miner which compiled well on rhel 6.X ?

'yum install libcurl-devel' might help. You will need gmp-devel too btw.

Precompiled binaries for Linux make really little sense as they are going to be big and not optimized for specific CPU as they are when you build locally.

[Yanakitu Tenatako]

Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms

[reorder]

Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms

We have now tuned servers to request a lot more shares of lower diff, to reduce stales. Please tell if it has helped.

[cubydu]

Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms

We have now tuned servers to request a lot more shares of lower diff, to reduce stales. Please tell if it has helped.

after 20 minutes..

Code:

[2014-08-04 10:15:07] accepted: 167/179 (93.30%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:08] thread 31: 385704 hashes, 52.82 khash/s
[2014-08-04 10:15:08] accepted: 168/180 (93.33%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:16] thread 22: 2428844 hashes, 52.73 khash/s
[2014-08-04 10:15:17] thread 9: 909500 hashes, 52.85 khash/s
[2014-08-04 10:15:17] accepted: 169/181 (93.37%), 1689 khash/s (yay!!!)

Please try again now, share difficulty reduced twice on the pool.

I have 50+ servers and can't mine with your pool.

Code:

[2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s

But when I mine with one server - all ok.

[reorder]

Code:

[2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s

But when I mine with one server - all ok.

This means your vardiff value has hiked too high. Please append unique suffixes to your workers usernames/addresses, for example, 'WALLET.SERVER1', 'WALLET.SERVER2' and so on so that they get a better vardiff each. Your displayed statistics will still be combined over all workers this way.