The payout times seem to be slipping ~ 15-20 mins every 24 hour period ...it is making it harder to calculate farms/rigs performamnce due to time not being exactly 1 hour
Can you go back to on the hour payouts or anytime but in 60 min iterations ??
Thanks
Topic: [ANN] [LTC] [PPS] [OTP 2FA] [Stratum only] LTCMine PPS mining pool (3.3%) - page 39. (Read 227582 times)
June 12, 2013, 12:42:46 AM
June 11, 2013, 05:09:55 PM
I use such settings just for very fast coins like wdc or dgc, with "-q 0 -s 1 -e 1", and dont use any for ltc mining.
I have 1.55% rejects, but may be this is because I'm in Russia, and Balthazars ltc server seems too.
LTC pool is based in Ukraine. I have 1.55% rejects, but may be this is because I'm in Russia, and Balthazars ltc server seems too.
June 11, 2013, 12:39:00 AM
I've try a default conf yesterday for a 8h run
A:2640 / R:26
"queue" : "1",
"scan-time" : "60",
"expiry" : "120",
you can try
A:2640 / R:26
"queue" : "1",
"scan-time" : "60",
"expiry" : "120",
you can try
June 10, 2013, 08:25:01 PM
Is this correct : --scan-time 30 --expiry 30 --queue 0
Thanks
EDIT: When I put the line as extra flags in Guiminer Scrypt Alpha the workers wont connect to the pool
Thanks
EDIT: When I put the line as extra flags in Guiminer Scrypt Alpha the workers wont connect to the pool
Try this: -Q 0 -s 30 -E 30
Thanks mate, the stales are just below 2% with the settings..still quite high
I use such settings just for very fast coins like wdc or dgc, with "-q 0 -s 1 -e 1", and dont use any for ltc mining.
I have 1.55% rejects, but may be this is because I'm in Russia, and Balthazars ltc server seems too.
June 10, 2013, 12:51:49 PM
Is this correct : --scan-time 30 --expiry 30 --queue 0
Thanks
EDIT: When I put the line as extra flags in Guiminer Scrypt Alpha the workers wont connect to the pool
Thanks
EDIT: When I put the line as extra flags in Guiminer Scrypt Alpha the workers wont connect to the pool
Try this: -Q 0 -s 30 -E 30
Thanks mate, the stales are just below 2% with the settings..still quite high
then.. -Q 0 -s 15 -E 15
June 10, 2013, 12:42:18 PM
Is this correct : --scan-time 30 --expiry 30 --queue 0
Thanks
EDIT: When I put the line as extra flags in Guiminer Scrypt Alpha the workers wont connect to the pool
Thanks
EDIT: When I put the line as extra flags in Guiminer Scrypt Alpha the workers wont connect to the pool
Try this: -Q 0 -s 30 -E 30
Thanks mate, the stales are just below 2% with the settings..still quite high
June 10, 2013, 07:50:46 AM
Azure
Could you send me PM with your payments log?
Could you send me PM with your payments log?
Done, thanks,
Azure
June 10, 2013, 07:33:38 AM
Azure
Could you send me PM with your payments log?
Could you send me PM with your payments log?
June 10, 2013, 07:22:38 AM
Just logged onto this thread after quite a while. I had noticed today my rewards showing very erratic numbers (some too low and some too high), even though my hashing rate was constant, and my overall daily expected reward total is lower than expected today; but the explanations I've seen here seem to have answered my question(s) I had regarding this. You're still going to recalculate them then? Thanks Balthazar.
Azure
Azure
June 10, 2013, 02:23:18 AM
No problem 
June 09, 2013, 09:38:59 PM
I know my rig is probably not finishing shares as the difficulty is too high before the block gets solved.
It seems that you are not quite well understood how it works. There is no "too high" or "too low" difficulty, and share can't be "finished".diff-1: hash < 0x0000ffff000000000000000000000000000000000000000000000000000000, one PoW hash per 65535 avg.
diff-256: hash < 0x000000ffff0000000000000000000000000000000000000000000000000000, one PoW hash per 16776960 avg.
Your OpenCL kernel searches the diff-1 hashes and then miner tries to test it with requested target (diff-256 in our example). If it matches the PoW condition, miner sends this result to pool, otherwise it tries another found hash. I.e. the share target it's just a filter for results of work which you are already done. Input/output data and the work amount per time interval always will be the same. With diff-256, for example, you will send 1/256 of diff-1 hashes which you are found. If you want to take a closer look on this process, try to start cgminer in debug mode
The only side effects of higher difficulty are
- lower speed calculation precision;
- slightly higher variance, but it doesn't matter with PPS.
Any reason for this increase in difficulty?
An attempt to decrease DB load/traffic usage and make average rejects ratio lower. Minimum diff will be decreased to 96-128 when new server will be available.Thanks for the detailed explanation. That will set my mind at ease.
June 09, 2013, 08:32:39 PM
I know my rig is probably not finishing shares as the difficulty is too high before the block gets solved.
It seems that you are not quite well understood how it works. There is no "too high" or "too low" difficulty, and share can't be "finished".diff-1: hash < 0x0000ffff000000000000000000000000000000000000000000000000000000, one PoW hash per 65535 avg.
diff-256: hash < 0x000000ffff0000000000000000000000000000000000000000000000000000, one PoW hash per 16776960 avg.
Your OpenCL kernel searches the diff-1 hashes and then miner tries to test it with requested target (diff-256 in our example). If it matches the PoW condition, miner sends this result to pool, otherwise it tries another found hash. I.e. the share target it's just a filter for results of work which you are already done. Input/output data and the work amount per time interval always will be the same. With diff-256, for example, you will send 1/256 of diff-1 hashes which you are found. If you want to take a closer look on this process, try to start cgminer in debug mode
The only side effects of higher difficulty are
- lower speed calculation precision;
- slightly higher variance, but it doesn't matter with PPS.
Any reason for this increase in difficulty?
An attempt to decrease DB load/traffic usage and make average rejects ratio lower. Minimum diff will be decreased to 96-128 when new server will be available. June 09, 2013, 07:09:04 PM
A few days ago I added support to keep track of your LTCMine.ru mining wallet balances to CryptFolio (thread). This helps you keep track of mining pool balances over time, and generates reports (such as your overall USD net worth).
I also added in a new feature to keep track of your mining hash rates as well (still being tested).
I also added in a new feature to keep track of your mining hash rates as well (still being tested).
June 09, 2013, 07:06:36 PM
I noticed today that my miners were getting much higher difficulty shares than normal. My 3 x 7950 rig usually gets around 200-300 difficulty on this pool and I just checked it now and I am getting shares in the 800 for difficulty. I know my rig is probably not finishing shares as the difficulty is too high before the block gets solved. Any reason for this increase in difficulty?
June 09, 2013, 02:19:59 PM
Don't worry. Everything that you sent is logged twice. 
June 09, 2013, 02:17:58 PM
My rewards for the previous hour of work is showing as 0.00413076, when I have 3.7mh on your pool. I was hashing the entire time today, even when your site was down all of miners still accepted shares. my average hourly rewards have been around .25 is everything okay on the rewards payout on your pool?
Seem something like this happens to me, too :\
June 09, 2013, 02:07:08 PM
My rewards for the previous hour of work is showing as 0.00413076, when I have 3.7mh on your pool. I was hashing the entire time today, even when your site was down all of miners still accepted shares. my average hourly rewards have been around .25 is everything okay on the rewards payout on your pool?
DDoS caused the problem with statistics update at this time. I have shares log and work will be recalculated. June 09, 2013, 01:57:36 PM
My rewards for the previous hour of work is showing as 0.00413076, when I have 3.7mh on your pool. I was hashing the entire time today, even when your site was down all of miners still accepted shares. my average hourly rewards have been around .25 is everything okay on the rewards payout on your pool?
June 09, 2013, 01:42:45 PM
Shares are accepted. But I see manual payments at 22:11:46, 22:10:57.
I've started payment script manually at this time, to check reindex operation effect. It doesn't affects your mining results.Do you recommend to use backup pool?
It's always recommended to setup backup pool(s). Even if everything is fine on your main pool. June 09, 2013, 01:36:34 PM
Hi Balthazar
I have the Payment at 19:49:08, is it because of DDOS?
Usually it is at
19:00:01
17:00:01
16:00:01
15:00:01
Thank you
It was the manual payment.I have the Payment at 19:49:08, is it because of DDOS?
Usually it is at
19:00:01
17:00:01
16:00:01
15:00:01
Thank you
Shares are accepted. But I see manual payments at 22:11:46, 22:10:57. Do you recommend to use backup pool?
Jump to: