Chat archive · 2017-04
GregoryGHarding · · #2482
GregoryGHarding · · #2483
VanessaEzekowitz · · #2484
Chris Sokolowski · · #2488
avgswsiss · · #2489
VanessaEzekowitz wrote: You asked earlier about reject percentage on Scrypt... for me it hit 2.4 percent (54334 accepted shares, 1302 rejected, over the course of 4 days, 16 hours)94.6% on my Scrypt, which means 0.35 GH rejected.
mickeekung · · #2490
mickeekung · · #2491
mickeekung · · #2493
FRISKIE · · #2494
avgswsiss · · #2495
avgswsiss · · #2496
mickeekung wrote: Anyone set c=x for x11? Could you tell me what is the best x for c=x to set?Have done with DASH, but during the days that there was a problem with lost blocks, which has been solved, as per Steve’s post. Haven’t tried any other, yet.
Steve Sokolowski · · #2497
avgswsiss wrote: Steve / Chris: Regarding x11 difficulty: Can you please provide us with more details how you consider difficulty for x11, and/or provide more informations for miners? As you know, i’m losing to much hashpower and have concluded that you allow max. 4.0 as a difficulty, otherwise, you set it dynamically. Thanks.Do you want that maximum difficulty to be changed?
Steve Sokolowski · · #2498
FRISKIE wrote: @ Steve/Chris - Nicehash is looking pretty good now . . if we can maintain this level of performance will be just fineRight now, I’ve gotten the load down from 150% (which caused delays) to 80%, which means we are able to process shares in real time. That means we’re safe for now, and over the weekend I should be able to make further improvements to stay ahead of new customers.![]()
avgswsiss · · #2499
Steve Sokolowski wrote:I dont know which formula you use, but, i think it needs to be increased and/or leave it up to miners.avgswsiss wrote: Steve / Chris: Regarding x11 difficulty: Can you please provide us with more details how you consider difficulty for x11, and/or provide more informations for miners? As you know, i’m losing to much hashpower and have concluded that you allow max. 4.0 as a difficulty, otherwise, you set it dynamically. Thanks.Do you want that maximum difficulty to be changed?
Steve Sokolowski · · #2500
avgswsiss wrote:What value would you like to use?Steve Sokolowski wrote:I dont know which formula you use, but, i think it needs to be increased and/or leave it up to miners.avgswsiss wrote: Steve / Chris: Regarding x11 difficulty: Can you please provide us with more details how you consider difficulty for x11, and/or provide more informations for miners? As you know, i’m losing to much hashpower and have concluded that you allow max. 4.0 as a difficulty, otherwise, you set it dynamically. Thanks.Do you want that maximum difficulty to be changed?
avgswsiss · · #2501
avgswsiss · · #2502
avgswsiss · · #2503
Steve Sokolowski wrote:It depends generally, but, usually i divide my GH to 1.4 or 1.8, but as said, increasing is necc. as its something that pool works based on SPM and allow miners to chose. in this case it all depends what your configuration is.avgswsiss wrote:What value would you like to use?Steve Sokolowski wrote: Do you want that maximum difficulty to be changed?I dont know which formula you use, but, i think it needs to be increased and/or leave it up to miners.
jinxorbit · · #2504
Steve Sokolowski · · #2505
avgswsiss wrote: @Steve- On Scrypt, last few days, i see more and more Duplicate share rejections, but also "Both primary and merge mined shares are stale". Any specific reason you may think about?See whether those issues continue today, after 8:00am EDT, and let us know.
crazyq3 · · #2506
crazyq3 · · #2507
Steve Sokolowski · · #2508
crazyq3 wrote: i have problem too on a4 dominator Duplicate share rejections, 125.27 MH/s (43.48%) Duplicate: 125.27 MH/sDo these problems occur all at once, or at a steady rate?
avgswsiss · · #2509
Steve Sokolowski wrote:Ok Steve. will try it, otherwise i will definitive be forced to leave your pool. I’m losing at least 1 GH/s scrypt from what i have connected here.avgswsiss wrote: @Steve- On Scrypt, last few days, i see more and more Duplicate share rejections, but also "Both primary and merge mined shares are stale". Any specific reason you may think about?See whether those issues continue today, after 8:00am EDT, and let us know.
crazyq3 · · #2510
Steve Sokolowski wrote:no not occur all at once, after 1-2 hours stand on pool simtime. and not alwayscrazyq3 wrote: i have problem too on a4 dominator Duplicate share rejections, 125.27 MH/s (43.48%) Duplicate: 125.27 MH/sDo these problems occur all at once, or at a steady rate?
Steve Sokolowski · · #2511
crazyq3 wrote:has this improved over the last week?Steve Sokolowski wrote:no not occur all at once, after 1-2 hours stand on pool simtime. and not alwayscrazyq3 wrote: i have problem too on a4 dominator Duplicate share rejections, 125.27 MH/s (43.48%) Duplicate: 125.27 MH/sDo these problems occur all at once, or at a steady rate?
avgswsiss · · #2516
avgswsiss wrote:is got now to 88.38%.Steve Sokolowski wrote:Ok Steve. will try it, otherwise i will definitive be forced to leave your pool. I’m losing at least 1 GH/s scrypt from what i have connected here.avgswsiss wrote: @Steve- On Scrypt, last few days, i see more and more Duplicate share rejections, but also "Both primary and merge mined shares are stale". Any specific reason you may think about?See whether those issues continue today, after 8:00am EDT, and let us know.
Steve Sokolowski · · #2517
avgswsiss wrote:Accepted shares are at 83%, or rejected ones are?avgswsiss wrote:is got now to 88.38%.Steve Sokolowski wrote: See whether those issues continue today, after 8:00am EDT, and let us know.Ok Steve. will try it, otherwise i will definitive be forced to leave your pool. I’m losing at least 1 GH/s scrypt from what i have connected here.
avgswsiss · · #2519
Steve Sokolowski wrote:accepted, but i-m moving.avgswsiss wrote:Accepted shares are at 83%, or rejected ones are?avgswsiss wrote: Ok Steve. will try it, otherwise i will definitive be forced to leave your pool. I’m losing at least 1 GH/s scrypt from what i have connected here.is got now to 88.38%.
Steve Sokolowski · · #2520
avgswsiss wrote:I’m glad to hear that we were able to improve the share acceptance rate, which seems to imply that performance was the issue. We’ll see if tomorrow’s last round of improvements fixes the issue for good.Steve Sokolowski wrote:accepted, but i-m moving.avgswsiss wrote: is got now to 88.38%.Accepted shares are at 83%, or rejected ones are?
GregoryGHarding · · #2521
Steve Sokolowski · · #2523
GregoryGHarding wrote: does block finder rewards get rewarded to the finder or split between everyone in the difficultyIt depends on what type of mining you choose. PPS mining is reliable but you don’t get the rewards for valuable blocks, while solo mining earns you nothing unless you find blocks.
maminhyuk · · #2524
maminhyuk · · #2525
CritterDog · · #2528
mickeekung · · #2529
CritterDog · · #2530
CritterDog · · #2531
mickeekung wrote: Knock Knock.A long-running task has delayed the recording of shares since 22 minutes ago. Statistics will be out-of-date until the task has completed and all shares have been recorded to the database. All miners disconnected.Yep my miners have gone to back up pool..
jinxorbit · · #2532
piet · · #2533
Nalith · · #2534
piet · · #2535
jinxorbit · · #2536
mickeekung · · #2537
jinxorbit · · #2538
CritterDog · · #2540
Chris Sokolowski · · #2541
CritterDog wrote: Also coins I forfeited a few weeks ago have returnedI refunded some shares that were inadvertently forfeit sue to a bug in our cheating script. It might have also inadvertently reversed some desired forfeitures.
Chris Sokolowski · · #2542
Steve Sokolowski · · #2543
CritterDog wrote: Don’t really like my miners switching back and forth from back up pool any idea when whatever will be fixed? For now I will switch to backup until things get settled here. ThanksThis should be fixed now. We deployed a new version to improve performance.
mickeekung · · #2545
mickeekung · · #2546
mickeekung · · #2547
olkah · · #2548
olkah · · #2549
mickeekung · · #2550
Steve Sokolowski · · #2551
mickeekung · · #2552
olkah · · #2553
Steve Sokolowski · · #2554
olkah · · #2555
olkah · · #2556
Nalith · · #2557
olkah · · #2558
Nalith · · #2559
CritterDog · · #2560
olkah · · #2561
olkah · · #2562
olkah · · #2563
Nalith · · #2564
JKDReaper · · #2565
mickeekung · · #2568
mickeekung · · #2569
piet · · #2572
piet · · #2573
galixxx · · #2574
piet wrote: i mined these coins 3 month ago...same for me on XMR...
jinxorbit · · #2576
FRISKIE · · #2577
dfair98 · · #2578
jinxorbit wrote: a4’s unstable on Prohasing, rolling over to another pool to check stability...have you tried adding the h password param?
jinxorbit · · #2579
Steve Sokolowski · · #2580
jinxorbit wrote: a4’s unstable on Prohasing, rolling over to another pool to check stability...We might have to buy one of these to figure out what is wrong. Let me know if this is something specific to this site or whether the situation improves elsewhere.
jinxorbit · · #2581
jinxorbit · · #2582
Steve Sokolowski wrote:The units running on the other pool are hashing fine. The one running on PH has one card shutdown and running at 35 degrees Celsius.jinxorbit wrote: a4’s unstable on Prohasing, rolling over to another pool to check stability...We might have to buy one of these to figure out what is wrong. Let me know if this is something specific to this site or whether the situation improves elsewhere.
jinxorbit · · #2583
jinxorbit · · #2584
CritterDog · · #2586
Chris Sokolowski · · #2587