0.5% fee - Pools - Central Cavern Mining Co - Pools - page 4.

Collider

hero member

Activity: 714

Merit: 500

Ping from Thor Datacenter to Iceland central cavern p2pool node:

Code:

64 bytes from 192.71.218.197: seq=34 ttl=63 time=0.385 ms
64 bytes from 192.71.218.197: seq=43 ttl=63 time=0.421 ms
64 bytes from 192.71.218.197: seq=44 ttl=63 time=0.427 ms
64 bytes from 192.71.218.197: seq=45 ttl=63 time=0.350 ms
64 bytes from 192.71.218.197: seq=46 ttl=63 time=0.377 ms
64 bytes from 192.71.218.197: seq=47 ttl=63 time=0.347 ms
64 bytes from 192.71.218.197: seq=48 ttl=63 time=0.368 ms

Under 1 ms! GOGO Blockhcain

can´t wait for it to be downloaded.

What is your ping from Scotland to them ras?

CentralCavern

newbie

Activity: 28

Merit: 0

Iceland Node, BTClockchain downloading.

raskul

sr. member

Activity: 434

Merit: 250

Quote from: Collider on June 20, 2014, 04:36:31 PM

Sure, just pm me and i can maybe try and help?

murdof is working on it now. it's an issue on the host regarding mirror downloading of install packages.
i've every faith that we'll be downloading the blockchain to the Iceland node over the weekend Grin

Collider

hero member

Activity: 714

Merit: 500

Sure, just pm me and i can maybe try and help?

raskul

sr. member

Activity: 434

Merit: 250

Quote from: Collider on June 20, 2014, 03:49:00 PM

They usually also allow you to use around 120% of the payed for hardware, sometimes even more if the actual server is on low load.

"Catastrophic" failure should therefore never occure, but checking the usage once per week is usually a good idea.

I check it daily, so no worries, i'll make sure anything that needs upgrading gets done in good time.
by the way, Collider... i'm having 'issues' with my VPS host in Iceland. I'll let you know when I resolve these problems.

Collider

hero member

Activity: 714

Merit: 500

They usually also allow you to use around 120% of the payed for hardware, sometimes even more if the actual server is on low load.

"Catastrophic" failure should therefore never occure, but checking the usage once per week is usually a good idea.

CentralCavern

newbie

Activity: 28

Merit: 0

Quote from: Acejam on June 20, 2014, 02:00:54 PM

Quote from: raskul on June 20, 2014, 11:48:10 AM

The EU node runs fine with the same specifications. However, these severs can easily be upgraded with any hardware needed.
I found the only merged coin which was a drain on resources, was Huntercoin; which has been removed from the node.

Once you get more traffic, that will change quite a bit.

As explained, the VPS we use are easily upgraded, so this is not an issue; thanks. Wink

Acejam

full member

Activity: 124

Merit: 251

Quote from: raskul on June 20, 2014, 11:48:10 AM

The EU node runs fine with the same specifications. However, these severs can easily be upgraded with any hardware needed.
I found the only merged coin which was a drain on resources, was Huntercoin; which has been removed from the node.

Once you get more traffic, that will change quite a bit.

raskul

sr. member

Activity: 434

Merit: 250

Quote from: Acejam on June 20, 2014, 11:39:09 AM

Quote from: raskul on June 20, 2014, 02:29:35 AM

Quote from: Collider on June 20, 2014, 02:26:58 AM

Where is middle east node located?

It will be Isreal; however my first instance was created with too little memory (I was tired and missed points on the setup), so i've scratched it and will be installing

2CPU 4GB RAM and 50GB SSD with unlimited bandwidth.

Are you merged mining? If so, you're going to need more RAM than that.

The EU node runs fine with the same specifications. However, these severs can easily be upgraded with any hardware needed.
I found the only merged coin which was a drain on resources, was Huntercoin; which has been removed from the node.

Acejam

full member

Activity: 124

Merit: 251

Quote from: raskul on June 20, 2014, 02:29:35 AM

Quote from: Collider on June 20, 2014, 02:26:58 AM

Where is middle east node located?

It will be Isreal; however my first instance was created with too little memory (I was tired and missed points on the setup), so i've scratched it and will be installing

2CPU 4GB RAM and 50GB SSD with unlimited bandwidth.

Are you merged mining? If so, you're going to need more RAM than that.

raskul

sr. member

Activity: 434

Merit: 250

Quote from: Collider on June 20, 2014, 02:26:58 AM

Where is middle east node located?

It will be Isreal; however my first instance was created with too little memory (I was tired and missed points on the setup), so i've scratched it and will be installing

2CPU 4GB RAM and 50GB SSD with unlimited bandwidth.

It seems it will be monday next week before I get around to it, i'd hoped to have both Iceland and Middle East completed by end of play today, the errors set me back a bit.

Collider

hero member

Activity: 714

Merit: 500

Where is middle east node located?

raskul

sr. member

Activity: 434

Merit: 250

update: Middle East node is currently downloading the Bitcoin blockchain Grin

Middle East node should be ready ~~in t-48hours~~ Tuesday 24 June 2014.

This will be a 1% fee node.
thank you.

specialed101

member

Activity: 70

Merit: 10

Hi all,

Thanks for the assistance with the difficulty settings. The tips were very helpful, and gave me some ideas on what else to look for.

This http://forum.netcodepool.org/forum/showthread.php?tid=238 kind of went along with one suggestion, and sure enough the numbers have improved, including reducing the rejects.

raskul

sr. member

Activity: 434

Merit: 250

small update: I have chosen the VPS companies I wish to use for Iceland and for the Middle East: waiting to hear back regarding pricing (and other things) and both (fingers crossed) should be active by Tuesday 24th June 2014.

EDIT: I'll see if I can get a USA server running at the same time. Wink

EDIT2: thanks again jonnybravo, very insightful, and good to know regarding the S2 rigs.

jonnybravo0311

legendary

Activity: 1344

Merit: 1023

Mine at Jonny's Pool

By the way... just for fun I figured I'd see what kind of ping I'd get for this server from my location (Near Philadelphia in the US):

--- pool.centralcavern.uk ping statistics ---
80 packets transmitted, 79 packets received, 1.2% packet loss
round-trip min/avg/max/stddev = 96.268/114.866/289.298/42.460 ms

Not terrible, but with an average of nearly 115ms, I'd see too many rejects.

jonnybravo0311

legendary

Activity: 1344

Merit: 1023

Mine at Jonny's Pool

Quote from: specialed101 on June 19, 2014, 01:42:02 PM

Hi,

Thanks for the quick response. I've only been messing with bitcoin mining for a few weeks now; so please excuse my ignorance. I had thought that it is the "difficulty" setting from the pool that is regulating how hard my miners are working. There have been some very brief peaks in the 1TH/s range for each miner, but they keep throttling down to the 800+ to 900+ GH/s range, underperforming by about 300 GH/s combined.

This underperformance could impact my potential payout by about 10%, right? I have to admit that it's nice that they are running quite a bit cooler when I use your pool. Grin

However, I would like to get them back up to 1TH/s each. Any ideas?

Because p2pool is a large network of individual nodes, it is the responsibility of each node to provide difficulty values. For example, if I look at my own node right now, I see the following:

Code:

2014-06-19 14:10:17.971807 New work for worker! Difficulty: 468.830432 Share difficulty: 1567138.331514 Total block value: 25.064672 BTC including 325 transactions
2014-06-19 14:10:18.010919 New work for worker! Difficulty: 468.830432 Share difficulty: 1567138.331514 Total block value: 25.064672 BTC including 325 transactions
2014-06-19 14:10:18.049984 New work for worker! Difficulty: 64.000000 Share difficulty: 1567138.331514 Total block value: 25.064672 BTC including 325 transactions
2014-06-19 14:10:18.090329 New work for worker! Difficulty: 468.830432 Share difficulty: 1567138.331514 Total block value: 25.064672 BTC including 325 transactions

The three miners with the difficulty of 468.830432 are ones that are using the default node's difficulty settings. The one with the 64.000000 difficulty has manually set the difficulty as I showed in my previous post.

As for why you're getting ~900GH/s as opposed to the 1TH/s you should be, are you by chance using an Antminer S2? If yes, I recommend you point it to another pool. The problem is in the custom version of cgminer that the S2 uses. That version doesn't play well with p2pool and as a result you'll see that it will only average between 800 and 900 GH/s. Kano has been working on creating a better driver for the S2, and to compile a new version of cgminer; however, due to the closed-source nature of Bitmain's software, he's been having a difficult time reverse engineering it successfully.

specialed101

member

Activity: 70

Merit: 10

Hi,

Thanks for the quick response. I've only been messing with bitcoin mining for a few weeks now; so please excuse my ignorance. I had thought that it is the "difficulty" setting from the pool that is regulating how hard my miners are working. There have been some very brief peaks in the 1TH/s range for each miner, but they keep throttling down to the 800+ to 900+ GH/s range, underperforming by about 300 GH/s combined.

This underperformance could impact my potential payout by about 10%, right? I have to admit that it's nice that they are running quite a bit cooler when I use your pool. Grin

However, I would like to get them back up to 1TH/s each. Any ideas?

raskul

sr. member

Activity: 434

Merit: 250

Quote from: jonnybravo0311 on June 19, 2014, 01:36:35 PM

Quote from: specialed101 on June 19, 2014, 01:08:35 PM

Hi,

Your pool sounds like just what I've been looking for, but it seems like my miners are hitting a ceiling of a "difficulty" of 999.98. I am used to seeing that as more of a dynamic value. Is that hard-coded on your pool?

The difficulty given out by a p2pool node is based on the total hash rate of the node. It's designed that way so the node doesn't get flooded with shares that have no chance of actually being an accepted block solution. There are two difficulty settings that are taken into account: pseudo and actual. The pseudo difficulty is the difficulty of shares your miner submits. The only real purpose of this is to make your graphs look pretty. The actual difficulty determines the value of your share relative to other miners. It is there to ensure that miners with high hash rates don't completely dominate the share chain. Again, this is calculated by the node. You can set your own values if you wish when you connect to the pool:

WALLETADDRESS/DIFF+PSEUDO

the /DIFF is the actual difficulty
the +PSEUDO is the pseudo difficulty

Let's give an example...

If you have a single S1 and you connect to a p2pool node that has a total hash rate of 100TH/s, you'll find that your S1 will very rarely find a share; however, when it does, that share will be worth more than "normal". Conversely, if you have that same S1 on a p2pool node where it is the only miner, you'll find that your shares are worth the "normal" value.

Hope this helps.

this helps a lot, thank you jonnybravo - I had split my miners between addresses and was puzzled as to why my !XXL! singles weren't accepting shares.
now I know. i'll pop them back and just wait Grin

jonnybravo0311

legendary

Activity: 1344

Merit: 1023

Mine at Jonny's Pool

Quote from: specialed101 on June 19, 2014, 01:08:35 PM

Hi,

Your pool sounds like just what I've been looking for, but it seems like my miners are hitting a ceiling of a "difficulty" of 999.98. I am used to seeing that as more of a dynamic value. Is that hard-coded on your pool?

The difficulty given out by a p2pool node is based on the total hash rate of the node. It's designed that way so the node doesn't get flooded with shares that have no chance of actually being an accepted block solution. There are two difficulty settings that are taken into account: pseudo and actual. The pseudo difficulty is the difficulty of shares your miner submits. The only real purpose of this is to make your graphs look pretty. The actual difficulty determines the value of your share relative to other miners. It is there to ensure that miners with high hash rates don't completely dominate the share chain. Again, this is calculated by the node. You can set your own values if you wish when you connect to the pool:

WALLETADDRESS/DIFF+PSEUDO

the /DIFF is the actual difficulty
the +PSEUDO is the pseudo difficulty

Let's give an example...

If you have a single S1 and you connect to a p2pool node that has a total hash rate of 100TH/s, you'll find that your S1 will very rarely find a share; however, when it does, that share will be worth more than "normal". Conversely, if you have that same S1 on a p2pool node where it is the only miner, you'll find that your shares are worth the "normal" value.

Hope this helps.

Topic: 0.5% fee - Pools - Central Cavern Mining Co - Pools - page 4. (Read 6366 times)