Pages:
Author

Topic: [POOL] --- Coinotron --- RavenCoin PPS: 1.5% ----- PPLNS, RBPPS: 0% --------- - page 98. (Read 295324 times)

legendary
Activity: 1182
Merit: 1000
We are introducing PPS/RBPPS payout algorithm in our Bitcoin Pool.

New system will be turned on at the beginning of BTC round #112. Simultaneously DGM system will be switched off.
All existing BTC workers will be automatically switched to RBPPS.  
All remaining ("buffered") DGM rewards will be credited to miners balances at the end of current round (#111).

Shares delivered via PPS/RBPPS worker will be rewarded with constant rate:  
RBPPS share value = 0.98 * 25 BTC * Share difficulty / Current BTC Difficulty  
PPS share value   = 0.965 * 25 BTC * Share difficulty / Current BTC Difficulty  

RBPPS means Round-Based Pay Per Share. It works like Like PPS with one exception: payouts are delayed till a block is found and confirmed by the network. If a found block gets orphaned, earnings relative to it are not paid.  
legendary
Activity: 1078
Merit: 1005
BTW I think that this PPC memory leak bug may be hidden somewhere in code responsible for checking work. Where are you checking every delivered share vs target, directly in your pool or by calling bitcoind rpc getwork?
I use the rpc getwork. Is it possible that it's not memory being lost but being maintained in a cache? Has ppcoin added any additional static global maps or caches?
legendary
Activity: 1064
Merit: 1000
If we are pretty sure getwork call is leaking massive amount of memory, I can maybe add some non-intrusive diagnostic code under debug mode for you guys to try.

Is there a rough estimate of how many getwork call is issued to ppcoind daily on the pool? A million?

Get-work may be part of it, but be aware that PPC explorer is also experiencing creeping memory leakage.

For example after restart and catch up last night ,ppcoind was using about 3.4% of the memory. Overnight it has creeped up to around 6% of the memory.

Just letting you know to keep that in mind.
legendary
Activity: 1205
Merit: 1010
If we are pretty sure getwork call is leaking massive amount of memory, I can maybe add some non-intrusive diagnostic code under debug mode for you guys to try.

Is there a rough estimate of how many getwork call is issued to ppcoind daily on the pool? A million?
legendary
Activity: 1182
Merit: 1000
200 GH - LTC pool
The main page of coinotron says 200 Mhash for LTC, but adds it up as Ghash. Is it mhash or ghash? Even 200 mhash strikes me as impressive for ltc.

Oh, my fault. Changed to MH. Smiley
BTW I think that this PPC memory leak bug may be hidden somewhere in code responsible for checking work. Where are you checking every delivered share vs target, directly in your pool or by calling bitcoind rpc getwork?
legendary
Activity: 1078
Merit: 1005
200 GH - LTC pool
The main page of coinotron says 200 Mhash for LTC, but adds it up as Ghash. Is it mhash or ghash? Even 200 mhash strikes me as impressive for ltc.
legendary
Activity: 1182
Merit: 1000
Good news everyone! Smiley

Today we have broken 2 previous records:
400 GH - combined hashrate of all sub-pools
200 MH - LTC pool

legendary
Activity: 1182
Merit: 1000
Another 10 min downtime of PPC pool to workaround memory leak issue.

Also, I have changed PPC share difficulty to 4. I just want to limit number of pool restarts.
This should decrease number of getworks and as a result slow down memory consumption by ppcoind.
legendary
Activity: 1182
Merit: 1000
10 min downtime of PPC pool to workaround memory leak issue.
legendary
Activity: 1182
Merit: 1000
Daaaaang... 4 BTC blocks mined in two days. What are the odds on that? It has to be really small considering the size of the BTC pool at Coinotron.

Of course they are all found when I have my rigs down to reorganize a little bit!! Damn the luck!

Yes it happened for a very first time. Looks improbable to me as well. But it is true.
To be honest I'm still pretty amazed by round length ranges observed in Bitcoin mining. In last two months shortest round took 1:36h while the longest one over 200h!

You don't have to worry. It is not proportional pool, it is DGM. Series of quick rounds don't affect miners gains.

BTW
I was planning to introduce PPS to BTC pool last Saturday but I postponed it until round 210000. It could be such a good start!
legendary
Activity: 1484
Merit: 1026
In Cryptocoins I Trust
Daaaaang... 4 BTC blocks mined in two days. What are the odds on that? It has to be really small considering the size of the BTC pool at Coinotron.

Of course they are all found when I have my rigs down to reorganize a little bit!! Damn the luck!
legendary
Activity: 1182
Merit: 1000
We have added SSL support. Our website forces all connections to HTTPS.
legendary
Activity: 1182
Merit: 1000
It would be alot more user friendly if workers payment method could be changed all at the same time rather than changing each one individually the way it is now. This image is wat i am trying to describe.


Very good idea. I will probably implement it when we will have uniform worker types for all coins ( i.e. when we switch BTC pool to PPS/RBPPS )
sr. member
Activity: 271
Merit: 250
It would be alot more user friendly if workers payment method could be changed all at the same time rather than changing each one individually the way it is now. This image is wat i am trying to describe.



sr. member
Activity: 350
Merit: 250
Tried to mine terracoin with same software mining litecoin and it doesn't work

is that supposed to work? or need the special terracoin sotware with its own miner

Terracoin does not use the scrypt algorithm litecoin uses, so using an scrypt-enabled miner, or more generally  cpu-mining @ terracoin or bitcoin won't give you much coins.


My question still isn't answered

Does terracoin require totally different mining software? not the same algorithm as btc nmc or ltc

You need to turn off the Scrypt engine and just use SHA2. TerraCoin is almost exactly like Bitcoin, not Litecoin which is based on a different hashing algorythm that is much more memory intensive and is not well suited to GPU (Well that didn't take long), FPGA, or ASIC.

It's possible you are not a troll, but honestly have missed this detail through all those posts, I try to give folks the benefit of the doubt. This is something that has been common knowledge for months however, especially among those that mine LTC (I do some) so you must forgive the rabid anti-troll squad.

Any other questions?
legendary
Activity: 1182
Merit: 1000
I'm just creating some space for other/next alt coins Smiley
legendary
Activity: 1420
Merit: 1010
FYI

Due to lack of popularity we decided to close LQC pool. Pool will be closed on 2012-11-17. Please withdraw your coins until 2012-11-30.

awww really!! Sad I liked to have LQC set as a backup for all my miners and occasionally jump on... not sure of other pools Sad Well just wanted to let you know I will be sad to see this go, but u got to do what u got to do i suppose
legendary
Activity: 1182
Merit: 1000
FYI

Due to lack of popularity we decided to close LQC pool. Pool will be closed on 2012-11-17. Please withdraw your coins until 2012-11-30.
420
hero member
Activity: 756
Merit: 500

CGMiner works perfectly well Smiley

and RPC miner do you know? or anyone

i get error: Could not retrieve work from RPC server.
CURL return value = 7
hero member
Activity: 616
Merit: 500
That is very good question.
Did you change worker type on website or user/parword in cgminer on your rigs?
Yes, No, No

Did this "magic" split last long? Coinotron uses 10 minutes average to calculate worker/user speed. Maybe you just observed averaged TRC and BTC hashrates being momentarily equal?
Hrm, I should of assumed that... that was probably the case. I'm not sure how long I switched them over, but it wasn't very long at all.

I will try to re-create the problem, but this time leave them on TRC for longer and see if the miners work themselves out. Hopefully the BTC miners delete themselves after ~10 minutes.

You'll see this as well if say you switch to another pool.. if you look 5 minutes later you'll see a hash rate split in someway between both pools.. as the numbers are some sort of timed average.


that said.. I DONT recommend having TRC and BTC pools in cgminer at the same time (I use a diff batch file for each)... the longpolls will eff everything up and cause cgminer to "freeze" with the WAIT status because it will get a new block info from the TRC pool and think the BTC pool is issueing work for an old block.
Pages:
Jump to: