Thanks for the quick and smooth trade earlier today Naster  My 0.03 BTC for PP. |
|
|
|
This is not surprising, there are many services that take even more,
example Bittrex, Kraken - 0.001BTC is around $13USD.
0.002 BTC on C-cex  |
|
|
|
WTF?!
Yeah, WTF |
|
|
|
Thanks for the testing. So in a nutshell you are saying the Ryzen will only use 35% of the processor no matter what proclimit is set, and both the 32 bit and 64 bit builds are essentially the same.
Ok, that sounds like a different problem than I had on the windows xeon 2 proc. The xeon on 64 bit only used 50% of the proc, but on 32 bit I got it to use 90% of the proc and on the pool it solves roughly what the linux equiv box solves.
Additionally, non use of resources is a different problem than was discussed after f7000 went live. The problem we looked at before was the hash rate drop on the servers compared to the laptops and the shares solved per HPS- while assuming the whole processor was being utilized. This is more of an issue where the processor is not being utilized.
I think I will have time to take a look at making a test miner that holds a reference to two KJV bibles.
In the mean time, the other thing that no one has reported is what happens when you run two copies of BBP against two different datadirectories on the Ryzen? If anyone can test that out and report back that would be immensely helpful also. I think inblue was going to try that on a server at one point.
Hmmm... same cpu as emdes and win10. Wallet 1.0.4.0 64bit On 16 genproclimit i get 100% usage and pc reacts like he is under heavy load... but hps2 is round 19k... I have problem with 35 cpu usage limit but not on this version. It's a random behaviour on one walllet i got on other not. I think It's connected to setting of genproclimit. If genproc reacys like 1 is 1 thread i dont have limit... but if on 16 i got 45% so you must like emdes said 32 to get hash2 above 20k And still get best hps on 6 genproclimit(in wallet) but hps2 is 9k. If i rise genproclimit hps will drop and hps2 will be bigger. But my optimal is 11 genproclimit. After that hps2 is droping again... like now on 16 i got 19k Im also getting the same in win10, 100% CPU load but low HPS2. win8.1 64bit = 20-30k HPS2 with 35% CPU load  |
|
|
|
 loot loot_x4 14577.78 15988.83 37 9/24/2017 8:49:29 PM <- Ryzen 1700x 1.0.4.0 64bit after 2 hours+ mining (take a look at the CPU load) Just bumped the genproclimit to 32, now im getting 32-35% CPU load again (and probably 20-25k HPS2) just check the leaderboard in a few hours. YES, I did some tests with lower genproclimits too, but the hashrate/shares/CPU load drops by 30-40% when using anything lower than 32. Waiting for Oliwer's genproclimit 11 test on the 32bit wallet EDIT: 30 minutes after switching back to genproclimit 32-> HPS1: 24189.32 HPS2: 29913.39 On 1.0.3.8 32bit genproclimit 11 i got HPS 20k and HPS2 17-18k cpu usage around 35-40% Now testing 1.0.4.0 on genproclimit 11... 1.0.4.0 64bit with genproclimit 32 - HPS 24k and HPS2 25k-ish with CPU load 32-37%. My HPS2 drops to 15k with SMT disabled btw. Did you disable it? |
|
|
|
loot loot_x4 14577.78 15988.83 37 9/24/2017 8:49:29 PM <- Ryzen 1700x 1.0.4.0 64bit after 2 hours+ mining (take a look at the CPU load) Just bumped the genproclimit to 32, now im getting 32-35% CPU load again (and probably 20-25k HPS2) just check the leaderboard in a few hours. YES, I did some tests with lower genproclimits too, but the hashrate/shares/CPU load drops by 30-40% when using anything lower than 32. Waiting for Oliwer's genproclimit 11 test on the 32bit wallet EDIT: 30 minutes after switching back to genproclimit 32-> HPS1: 24189.32 HPS2: 29913.39 |
|
|
|
Thanks for the explanation. So it basically favor mid side cpu? I will reduce the thread to see what will happen.
Only the shares count for the earning, am I right?
Also can I use one worker for two computers in the pool?
Yes, ironically we had a rocky start where the Ryzens and the Xeons were killing the small procs, and unintentionally, the mid-level CPUs seem to be winning now. You can now point multiple CPUs to one workerID and the HashPerSec2 will reflect both. Its probably better to start out keeping all workerids separate so you can see what you hashpersec2 reading starts out as. 10 year old 4cores better than a new 8core ryzen I doubt it, ensure you were mining on both for a few hours and then post the HPS2 here from both test subjects. loot loot_x4 23735.33 22137.79 49 9/24/2017 5:01:07 PM <- Ryzen 1700x @ 3400mhz loot loot_x2 17155.16 20658.28 48 9/24/2017 5:00:40 PM <- AMD 965BE @ 2900mhz YES, Ryzen still running at 35% load. Like I told you weeks ago. NO, im not switching to linux |
|
|
|
Just check the leaderboard:
HPS HPS2 Shares
22749.38 35995.53 83
150617.87 34167.42 77
22809.53 32594.31 75
59652.37 32352.97 75
22k get similar HPS2 with 150k HPS. Will they get similar earning? What kind of machine do you use, inblue?
Is the fast cpu solve hard share with high difficulty but get less share weight comparing with middle level cpu? So better to use a middle level cpu.
Would it be better to solo with the 150k VS the 22k ? Would it find a block 6 times faster than the 22k ? |
|
|
|
Thanks for the explanation. So it basically favor mid side cpu? I will reduce the thread to see what will happen.
Only the shares count for the earning, am I right?
Also can I use one worker for two computers in the pool?
Yes, ironically we had a rocky start where the Ryzens and the Xeons were killing the small procs, and unintentionally, the mid-level CPUs seem to be winning now. You can now point multiple CPUs to one workerID and the HashPerSec2 will reflect both. Its probably better to start out keeping all workerids separate so you can see what you hashpersec2 reading starts out as. 10 year old 4cores better than a new 8core ryzen |
|
|
|
i reinstalled windows i have bible pay up and running how do i recover my original wallet or is it all online? i did a backup before reinstall but i dont see where i can get back to my original wallet?
Just move your wallet.dat file to the same folder as your biblepay.conf file (Appdata->Roaming->Biblepay) and restart the wallet  |
|
|
|
How many threads from one IP address is allowed?
40 currently. Once Westwarnsworth's comes online, we can probably raise it. 40 on one pool, or 40 total pool1 and pool2 ? EDIT: Just moved my genproclimit 32 CPU over to pool2 for testing |
|
|
|
is capping the thread count an improvement ? Wondering the same, 40 thread limit is very low for many. Previous limit looked good to me since there are 64 core machines that can pull a lot more threads. @bible_pay would appreciate updates on the changes as well as how to counter the difficulty vs subsidy fluctuations, which seems to be pretty drastic. You should not need more than 20 threads with this algo, a lot have posted the higher the threads over 20 actually lower the performance. Anyway, we cant raise the limit until we have more pools. The latest version has not been released because it didnt do much for xeons. But, the biggest improvement for xeons is to run the 32bit wallet. That doubled the speed. Im only getting 10k HashesPerSecond2 in Win10, tested with everything from 2->32. In Win8.1 im getting 20-30k with genproclimit 32 (hashrate and CPU load dropped ALOT with genproclimit 4, 8, 16 or 20 VS 32) EDIT: Had to bump the genproclimit on all my CPU's 2-3x higher after installing 1.0.3.8 to get any hashrate/CPU load at all VS 1.0.3.7 (Win7, 8.1 and 10) on 2,4,6 and 8core CPU's. They all had the same "problem" |
|
|
|
C-cex wallet still in maintenance, and 24 volume so small because of that.. i am not sure but this brings kind of bad image.
I'm going to notify them soon to bring it from maintenance. I'm just about ready to check the logs to ensure the error is no longer present. That was..... soon  |
|
|
|
Is the pool down or did I my IP's get banned?
Down for me too |
|
|
|
but still isnt full power like on linux = ROBERT can you check continuously? there is still place for improvement You and your Oliwer mate are such slave drivers... i wouldnt want to work for u =D =D How about , pay him? And he "might" actually focus on what "you" want. =D Not a bad idea. On other pools, I always set my fee's to 2-5%. |
|
|
|
I don't care about the lower hashrate/payouts, but it's not really "fair" when linux get 2x hashrate on the same hardware. Just wanted to know why Guys- Its not getting ignored- we were moving like a steamroller until F7000 hit, and the issue is things have to be prioritized. Its a higher priority to address Prod issues than "hashrate" issues. Now it appears the pool is running again without issues so now I can take a look at the hash rate issues across OS. The pool is storing the OS flavor per miner now, so I should be able to go in and write a report of average speed per OS flavor. I do see that windows appears to hash at a much slower rate than linux for some reason. Im seeing 34,000 HPS on my vultr-debian vs 4,000 on my dual CPU xeon windows web server. Quite a disparity there. Definitely unintentional from our engineering standpoint. Yeah im not asking you to magically fix it over night, just look into it. Thanks |
|
|
|
I don't care about the lower hashrate/payouts, but it's not really "fair" when linux get 2x hashrate on the same hardware. Just wanted to know why |
|
|
|
A friend just told me that his hashrate dropped from 11k Hashps1 25-30k Hashps2, now he's getting 8k and 6k (Intel CPU) just by upgrading from 1.0.3.4 to 1.0.3.7 (same conf file). So it's not only me |
|
|
|
Sorry guys, have my son today, so I cant go into much detail.
Luckily, Ive got this new RDP program for my iphone so I was able to restart the pool remotely.
Anyway, 1.0.3.7 is finally out for download for windows.
Please upgrade, this version should reveal what is causing the pool to go down.
I will unban any nodes that are banned now.
Thanks. The nodes are mining for a while and dropping off from the pool btw. [Linux, 1.0.3.7] I tried deleting the banlist, debug files and clearing the bans as well with no avail. I think we got most of the problem resolved regarding dropping from the pool - they were dropping over the last 2 hours because Ive been debugging the data and clearing the pool. There was actually an issue where the pool couldnt handle a certain number in the uint256 (thats a really long number) and its been fixed. If you are on 1037, let me know if you drop now on either OS on the leaderboard- you shouldnt. The "stale block" and the "please upgrade" messages are fixed also. I cant ask ccex to upgrade until I verify the log has eliminated the read from disk error, but last night I added a couple more circumstances so we might be closer. Hashrate dropped in Windows. Any idea why ? We all dropped about 70%- when F7000 hit. Please compare configuration with linux on the same hardware config? Posted my hashrates many times. Used the same conf file, but it drops with every new wallet. Tiras getting 2 - 3 times higher hashrate in linux than me, Slovakia and oliwer21 does in windows, with the same CPU |
|
|
|
|
Show Posts
