Worst pool, eight hours 0.38 CNC Speed 2Khs
Btw I assume you mean 2000Kh/s? at 2Kh/s 0.38 CNC would be a good payout
Topic: [ANN][CNC][P2pool] - ChinaCoin (CHNCoin) P2Pool - 1% Fee - Stable and Fast! - page 3. (Read 8289 times)
May 06, 2013, 02:31:40 AM
Btw I assume you mean 2000Kh/s? at 2Kh/s 0.38 CNC would be a good payout
May 06, 2013, 02:09:48 AM
anyone care to comment on payouts (whether good or bad!)? personally im seeing more or less expected payouts at 1200KH/s, the payout statistics on the graphs page seem wrong though, I get sometimes more and sometimes less than reported there, not sure why the stats are not correct, check your wallet to see if you are getting expected payouts (looking at 2 or 3 hour periods, since this is PPLNS there is variance)
May 06, 2013, 01:49:51 AM
did some more testing and for me Scantime=1 and Expiry=1 seems to slightly lower rejects compared to Scantime=5 and Expiry=5
so I recommend to use Scantime 1 and Expiry 1 for the moment, anyone else observed this?
updating first post cmdline's accordingly
so I recommend to use Scantime 1 and Expiry 1 for the moment, anyone else observed this?
updating first post cmdline's accordingly
May 06, 2013, 12:25:55 AM
just noticed that even though you use the cmdline options for cgminer from the first post it might not set the Scantime and Expiry correctly (e.g. if you had a slightly corrupted cgminer.conf file, which I just found out to be my case), which is quite important to get good results.
You can check (or change) if the values are correct (Scantime: 5, Expiry 5) by pressing S while cgminer is running, then press S again to change the Scantime to 5, then E to change the Expiry to 5 if they are not, e.g. it should look like this:
This should reduce rejected shares in most cases if you were running with Scantime 60 and Expiry 120 before, which are the defaults
You can check (or change) if the values are correct (Scantime: 5, Expiry 5) by pressing S while cgminer is running, then press S again to change the Scantime to 5, then E to change the Expiry to 5 if they are not, e.g. it should look like this:
Code:
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 74.0C 2092RPM | 214.9K/216.3Kh/s | A:46 R:15 HW:0 U:6.42/m I:17
--------------------------------------------------------------------------------
[Q]ueue: 1
[S]cantime: 5
[E]xpiry: 5
[W]rite config file
[C]gminer restart
Select an option or any other key to return
This should reduce rejected shares in most cases if you were running with Scantime 60 and Expiry 120 before, which are the defaults
May 05, 2013, 11:42:35 PM
Worst pool, eight hours 0.38 CNC Speed 2Khs
Btw I assume you mean 2000Kh/s? at 2Kh/s 0.38 CNC would be a good payout
May 05, 2013, 11:39:42 PM
Worst pool, eight hours 0.38 CNC Speed 2Khs
so sorry, the pool was down for a couple hours - if you had a failover server defined in cgminer it probably mined there, its only up since 2.5 hours again
May 05, 2013, 11:38:58 PM
pointed 1 of my rigs that has 1200 kh/s all I got 99% of the time is requested restart and over 5min I got 8 shares....any other time would be 10X that amount
in cgminer you will see lines like this constantly (like every couple seconds):
Quote
[2013-05-06 12:29:34] Stratum from pool 0 requested work restart
This is normal operation of P2Pool, it doesnt affect your payout. The low number of shares is also expected as P2Pool only counts shares with high enough difficulty, this is also normal operation, Im seeing the same on my 1000KH/s rig.
I have 1200kh/s pointed at the pool, according to http://cnc.strament.com/calculator.php that should net 101.7 CNC per 24 hours, or 4.23 per hour.
I started mining again when the pool was up exactly 2.5 hours before now, since then I have received 8.5 CNC, at the theoretical rate I should see 10.575 CNC for 2.5 hours work, so its about 2 CNC short. Given that all CNC P2Pools I have seen, including this one, have about ~20% DOA Shares, that would account for the missing ~2 CNC.
So Im assuming so far the payouts are working as expected given the ~20% DOA shares, please report your own payouts if you suspect any issues.
May 05, 2013, 11:32:23 PM
Worst pool, eight hours 0.38 CNC Speed 2Khs
May 05, 2013, 11:09:38 PM
pointed 1 of my rigs that has 1200 kh/s all I got 99% of the time is requested restart and over 5min I got 8 shares....any other time would be 10X that amount
May 05, 2013, 09:52:19 PM
up again! sorry was offline and there was a DNS issue fixed now
efficiency currently at 120% after some further server tweaks
fixed nowefficiency currently at 120% after some further server tweaks
May 05, 2013, 03:56:20 PM
Down for a few hours for me. Off to another p2pool....grrrrrrrrrrr.
May 05, 2013, 02:36:30 PM
you can try the following, the p2pool server sets the difficulty dynamically otherwise:
Tips to reduce DOA rate:(taken from Narken's thread)
You can set your share difficulty by adding +0.0000xxxx to your CHNcoin adress:
yourCNCaddress+0.0004872
Recommend share difficulty:
Hash Rate (KHash/s) Difficulty
1 +0.00000116
5 +0.00000582
10 +0.00001164
50 +0.00005821
100 +0.00011641
250 +0.00029103
500 +0.00058207
750 +0.00087310
1000 +0.00116414
Could anyone elaborate how does it work exactly, I set those +0.xxx in cgminer configs, but I've got several rigs and each has several cards.. is it set per address (since it's address+0.xxx) and therefore all hashing power combined, or per rig (all cards' in one rig hashrate combined) or per card in rig (if so, which card since there are different cards in one rig)? I played with those "+0.xxx" options but not only that didn't help with rejected rate (~30-35% in my case which is really A LOT Tips to reduce DOA rate:(taken from Narken's thread)
You can set your share difficulty by adding +0.0000xxxx to your CHNcoin adress:
yourCNCaddress+0.0004872
Recommend share difficulty:
Hash Rate (KHash/s) Difficulty
1 +0.00000116
5 +0.00000582
10 +0.00001164
50 +0.00005821
100 +0.00011641
250 +0.00029103
500 +0.00058207
750 +0.00087310
1000 +0.00116414
) I've also had "cgminer has stopped working" on one of the faster rigs (4*7970s) after a few minutes of running with that "+0.xxx" option set.You set it per miner per card based on the card's hashrate. But test it around for best options.
See more tips in my thread if needed:
https://bitcointalksearch.org/topic/anncncp2pool-for-chncoin-on-100mbit-line-with-low-latency-193216
May 05, 2013, 01:53:04 PM
seems like theres some issue?
not sure that number is accurate, afaik thats the payout for the default address of the pool only, its not accurate and it fluctuates between 0 and peanuts
im going to be off for the next couple hours, cross fingers!
May 05, 2013, 01:44:47 PM
it this correct?
May 05, 2013, 01:12:30 PM
you can try the following, the p2pool server sets the difficulty dynamically otherwise:
Tips to reduce DOA rate:(taken from Narken's thread)
You can set your share difficulty by adding +0.0000xxxx to your CHNcoin adress:
yourCNCaddress+0.0004872
Recommend share difficulty:
Hash Rate (KHash/s) Difficulty
1 +0.00000116
5 +0.00000582
10 +0.00001164
50 +0.00005821
100 +0.00011641
250 +0.00029103
500 +0.00058207
750 +0.00087310
1000 +0.00116414
Could anyone elaborate how does it work exactly, I set those +0.xxx in cgminer configs, but I've got several rigs and each has several cards.. is it set per address (since it's address+0.xxx) and therefore all hashing power combined, or per rig (all cards' in one rig hashrate combined) or per card in rig (if so, which card since there are different cards in one rig)? I played with those "+0.xxx" options but not only that didn't help with rejected rate (~30-35% in my case which is really A LOT Tips to reduce DOA rate:(taken from Narken's thread)
You can set your share difficulty by adding +0.0000xxxx to your CHNcoin adress:
yourCNCaddress+0.0004872
Recommend share difficulty:
Hash Rate (KHash/s) Difficulty
1 +0.00000116
5 +0.00000582
10 +0.00001164
50 +0.00005821
100 +0.00011641
250 +0.00029103
500 +0.00058207
750 +0.00087310
1000 +0.00116414
) I've also had "cgminer has stopped working" on one of the faster rigs (4*7970s) after a few minutes of running with that "+0.xxx" option set. 
May 05, 2013, 01:05:46 PM
very true, actually its possible to change payout to last 20 blocks for example, i just took the settings from blastbob's network, so if I change this now Im not sure I can stay connected to his network, currently the node has about 40MH/s though, so it would be feasible to give it a shot and disconnect from the network and push the payout to spread over 20 blocks
Don't risk messing your setup, if this is something you decide to do, see if bob is agreeable to doing the same, then you should have less problems.
For me personally I don't think it would matter too much, I'm after a completely different setup, one that counts shares since the last block was found and then pays out instantly, so with 10% of the shares I'd get 10% of the payout, if that takes a second or an hour then that's standard variance that I can live with.
PPLNS serves no purpose on P2Pool IMHO (**newbie so if it does I'd love to understand why), the pool has no risks of going broke with bad luck, it only pays out what it recieves minus a fee for profit.
Thanks for taking the time to respond, like I said earlier not having a dig at you or any other pool ops, keep up the good work
May 05, 2013, 01:03:28 PM
The share difficulty here is so insanely high that my miner can't put in work between blocks. Can you lower it?
you can try the following, the p2pool server sets the difficulty dynamically otherwise:
Tips to reduce DOA rate:(taken from Narken's thread)
You can set your share difficulty by adding +0.0000xxxx to your CHNcoin adress:
yourCNCaddress+0.0004872
Recommend share difficulty:
Hash Rate (KHash/s) Difficulty
1 +0.00000116
5 +0.00000582
10 +0.00001164
50 +0.00005821
100 +0.00011641
250 +0.00029103
500 +0.00058207
750 +0.00087310
1000 +0.00116414
May 05, 2013, 01:01:41 PM
gonna try & cpu mine here again for an hour, see what results we get..
May 05, 2013, 12:51:02 PM
The share difficulty here is so insanely high that my miner can't put in work between blocks. Can you lower it?
May 05, 2013, 12:35:11 PM
I'm just trying to understand why they are set up this way rather than since the last found block, I can accept the variance of finding blocks but this then adds another layer of variance on top.
There have been many posts about not getting payments, or getting less than expected and people then leave. Surely it's in a pool ops interest to have more people on the pool. That lowers the variance and increases the fees so everyone gains, and I'd stick with one over a pushpool pplns.
There have been many posts about not getting payments, or getting less than expected and people then leave. Surely it's in a pool ops interest to have more people on the pool. That lowers the variance and increases the fees so everyone gains, and I'd stick with one over a pushpool pplns.
very true, actually its possible to change payout to last 20 blocks for example, i just took the settings from blastbob's network, so if I change this now Im not sure I can stay connected to his network, currently the node has about 40MH/s though, so it would be feasible to give it a shot and disconnect from the network and push the payout to spread over 20 blocks
Jump to: