Bible Pay

TestNet => Active Discussions => Topic started by: Rob Andrews on February 07, 2020, 10:28:39 AM

Title: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 07, 2020, 10:28:39 AM
RandomX Integration


Welcome to the Biblepay-RandomX Integration Testing thread.

In this thread we will be testing:
Dash 0.14.0.5 changes (these occurred between Nov 2019 and Jan 2020).  These include: https://github.com/biblepay/biblepay-evolution/commit/34851a046392e169fcfa90a0bbcd7a01e1096090 which are ddos and chainlocks enhancements.
Test BiblePay Core RandomX hashes, RandomX solo mining, RX multithread solo mining.
Test xmrig->bbpcore mining against bbpcore using RX.
Test xmrig dual-hash mining.
Test bbp->nomp pool mining.
Stress test biblepay; verify RAM utilization and reliability in running for days.
Test BBP against sancs; regression test sanctuary abilities.
Verify how many BBP memory footprints can fit on a VM.




Starting Version:    1.5.0.2+


(Please ensure your version is greater than this, otherwise your testnet branch will not sync.  We are at block  ____28050_____________ as of February 9th, 2020).
BlockHash 28189:
c6fd*****


Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepayevo64develop.exe
     Linux PC 64bits Daemon:     https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
     Linux 64 bits QT:       https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz
     MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg

Not ready:
(Unknown state)
       Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz


To self compile:
https://github.com/biblepay/biblepay-evolution/blob/develop/BuildBiblePay.txt
** Note above:  The instructions have changed, see the changes for randomx.  **

The ETA for MainNet for RandomX  is   April 30th, 2020.




CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepayevolution



Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepayevolution/testnet3 folder.


NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

__________________________________________________________________________________________________________________________________________________________________________________________


POOLS for TESTNET (RandomX):

http://rxtest.biblepay.org


Instructions to pool mine:

Launch xmrig.exe or xmrig with these args:

xmrig-bbp-win64.exe -o rxtest.biblepay.org:3008 -u your_biblepay_testnet_address -p your_monero_prod_address --threads nproc_count

Where your bbp receive address for testnet receives Biblepay rewards, and your monero prod address receives prod rewards.


___________________________________________________________________________________________________________________________________________________________________________________________
XMRIG - The dual-hash miner for Biblepay + XMR:

To download Xmrig - binaries are here:

linux-64-bit :  https://github.com/biblepay/xmrig/raw/master/binaries/xmrig-bbp-linux64
windows-64-bit:  https://github.com/biblepay/xmrig/raw/master/binaries/bbprig.zip
(Extract the zip file to a folder on your machine, such as c:\mining\).  Run the miner from a batch file in that subdirectory (this allows the miner to use the dependencies).

To build your own xmrig:
https://github.com/biblepay/xmrig

How to mine:
xmrig-bbp-win64.exe -o rxtest.biblepay.org:3008 -u your_biblepay_testnet_address -p your_monero_prod_address --threads nproc_count
Where your bbp receive address for testnet receives Biblepay rewards, and your monero prod address receives prod rewards.

___________________________________________________________________________________________________________________________________________________________________________________________

How to get a monero production wallet, without running the full monero client (How to get an XMR address to mine to):
Since it is not allowed to mine to SX, we need to go with the next best option.
I'm sure other SPV wallets exist, but I'm currently using this one:

https://mymonero.com/

Just install it, then create a wallet.  Then use that address for your mining reward address.
NOTE:  The XMR side of the pool has a complicated payment strategy that we will explain asap.    For now know that XMR is held until the balance gets to 1xmr, but we will explain how to lower the threshhold etc.

The BiblePay payment side works the same as usual:  After the mined block matures in the pool, all the BBP is dispersed automatically.
____________________________________________________________________________________________________________________________________________________________________________________________


What is so special about XMR+BBP dual-hash mining?  What entices me as an XMR miner to mine BiblePay+XMR?



How does this work, why am I earning double what I earn in XMR alone?

The way it works is when you mine XMR alone, the solution can only go to one pool because you are solving a blockheader based on the current height and time and nonce for Monero.
However, BiblePay, with RX integrated can also be solved *at the same time*.  How?  Every randomx hash is checked against our current height and difficulty, giving you one chance to win a biblepay block for every XMR hash.


Why is biblepay interested in integrating wtih XMR?

We are interested because we want more miners, because miners give us more PR.  And we want to help more orphans.  Theoretically, the more XMR miners that dual-hash-mine, the more of our 10% tithe goes to orphan-charity.  That is a win-win for us, XMR, and the orphans!

How are the payments allocated for the work I spend mining?

For every 100,000 hashes, 90,000 go toward your personal account and 10,000 toward our orphan-charity XMR address (IE we tithe 10% to orphan charity, dispersed in XMR liquidations to our charity partners).  Out of the 90,000 that go toward your personal account, every single hash has an equal chance at winning a BBP block.  On the biblepay side, we pay out 100% of the earnings to your personal BBP address (we keep no overhead, unless a pool charges a small bit of overhead, TBD).   On the orphan-charity side that we spend from our collected revenue for our foundation, our liquidated XMR is guaranteed to go 100% to our voted charity (with no overhead kept by us).  We only partner with charities who are 75%+ efficient, such as compassion.com, Cameroon-one, Kairos, etc (therefore the maximum passes through to the children in need.  You can also see our orphan collage at https://accountability.biblepay.org).

__________________________________________________________________________________________________________________________________________________________________________________________________

Hashrate comparison chart, supplied by earlzmoade, showing a 200% increase in hashrates between xmrig plain vanilla and xmrig dual mode:

https://wiki.biblepay.org/RandomX_Hashing_Speed_Comparison









Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 08, 2020, 03:14:49 PM
Exciting times!  We look forward to an influx of thousands of randomx miners into biblepay to help donate to orphan charity!

Let's get started by simply testing the core wallet first.


For now, please restart the node with -erasechain=1 as transitioning to the first randomx block will tell you 'block index needs rebuilt, rebuild now?'  If you do not start with an empty chain, you can do that rebuild also.  Please see the op post for the blockhash and the block number.

Once we confirm this, then let's try solo mining.

Note that solo mining from the BBPcore wallet is 40 times slower than xmrig mining.  This is because the rx-core small-footprint algo is designed to conserve ram and is designed for syncing, and for efficient use of resources on sancs (this lets sancs run multiple copies and exchanges run bbp without kicking us off the exchange).

Each biblepaycore solo mining thread uses up 256meg of ram (due to the randomx virtual machine).  BE Very Careful about how you start the miner!  As you can crash biblepay if you attempt to use all your machine's ram at once.  For example, first test it with 'setgenerate true 1'.  Then increase to 3.  Slowly increase to see how much ram you can tolerate losing on your machine. 

Know that it will never be profitable to solo mine using the built in miner - because it is tuned for syncing and core efficiency.  The purpose for the solo miner is to allow us to debug when all nodes have failed (IE testnet) and ensure randomx is working.  In prod, most likely everyone will be running xmrig. 

The randomx-nomp pool is almost ready.  But please dont try it yet.

We will need to revive our sancs.  Technically since the chain in testnet is still intact this should just mean 'exec revivesanc sancname'.

Good luck everyone!

Let's hope this project breathes new life into Biblepay and puts us in the top 50!

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 08, 2020, 06:48:25 PM
Ok, now 3 versions are ready:

Windows 64

Linux 64 bit biblepayd

Linux 64 bit QT

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 08, 2020, 06:58:10 PM
I just did a rough calculation, and it may be possible that just 8 new randomx miners would be able to support 1 Venezuelan orphan.

($25 of mining revenue per month = $2.50 towards orphan-charity, roughly) and at our potential wholesale rate, that means just 8 miners could sponsor one orphan.

I look forward to this test scenario.  We really can make a huge impact in the world if the goal is reached.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 08, 2020, 08:49:34 PM
See OP post - XMRig has been released for windows and linux.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 09, 2020, 08:50:36 AM
** Pause Testing **

Ok, I was able to mine up until the superblock, but since we have no sancs, this exploited a problem.

In creating a solution I have discovered a bug that needs fixed; so please halt testing until the next mandatory upgrade.


Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 10, 2020, 10:44:57 PM
BiblePay - Mandatory Upgrade for TestNet
1.5.0.2f

- Make randomx compatible with GSC superblocks



* See OP Post for updated blockhash.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 11, 2020, 10:16:17 AM
BiblePay - Mandatory Upgrade for TestNet
1.5.0.2f

- Make randomx compatible with GSC superblocks



* See OP Post for updated blockhash.

Ok everyone, it looks like testing is ready now.

- Windows, linux and mac binaries are released now.

- Remember to start with a clean chain, just pass -erasechain=1 when you start (this should get you over the hump at the randomx_cutover_height).

- The xmrig miner is ready, go ahead and download it and try it.

- The randomx nomp pool is up:    rxtest.biblepay.org
(I realize I have some hps ratios and labels to update still, but it appears to be functioning in a primitive form now).

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 11, 2020, 11:47:27 AM
This for sure is a nice step for   biblepay i think.

I will try testnet on one of my ryzen 1600s machine.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 12, 2020, 01:42:57 PM
So i tried to run xmrig-bbp miner but i just get this message  " The code execution cannot proceed because VCRUNTIME140_1.dll was not found"
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 12, 2020, 04:13:47 PM
So i tried to run xmrig-bbp miner but i just get this message  " The code execution cannot proceed because VCRUNTIME140_1.dll was not found"

Hi, please tell us your bitness and OS, and please paste the command line you used so I can reproduce?  (Please be sure to paste the exact command line so I can trace the filename also).

Thanks.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: sunk818 on February 12, 2020, 10:34:21 PM
Hi, please tell us your bitness and OS, and please paste the command line you used so I can reproduce?  (Please be sure to paste the exact command line so I can trace the filename also).

Thanks.


I have same error:
https://github.com/biblepay/xmrig/blob/master/binaries/xmrig-bbp-win64.exe (https://github.com/biblepay/xmrig/blob/master/binaries/xmrig-bbp-win64.exe)
Using Windows 10 64-bit
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: oncoapop on February 13, 2020, 01:46:20 AM
Results from compiling the Linux ubuntu 18.04 version from source,

Platform: Linux 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU
Hardware: 6 x vCPU x Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz with 16 Gb RAM (VPS)

Repo:
git clone http://github.com/biblepay/biblepay-evolution

Code: [Select]
# RandomX Part
>cd biblepay-evolution/src/crypto/RandomX

>biblepay-evolution/src/crypto/RandomX: No such file or directory
The directory also does not appear in the source repo

https://github.com/biblepay/biblepay-evolution/tree/master/src/crypto

Finally compilation halts with the following message:
Code: [Select]
In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9971: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[2]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[2]: Leaving directory '/home/xmrbbp/biblepay-evolution/src'
Makefile:11657: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/xmrbbp/biblepay-evolution/src'
Makefile:686: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Advice would be greatly appreciated!

Thanks.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 13, 2020, 08:33:22 AM
Results from compiling the Linux ubuntu 18.04 version from source,

Platform: Linux 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU
Hardware: 6 x vCPU x Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz with 16 Gb RAM (VPS)

Repo:
git clone http://github.com/biblepay/biblepay-evolution

Code: [Select]
# RandomX Part
>cd biblepay-evolution/src/crypto/RandomX

>biblepay-evolution/src/crypto/RandomX: No such file or directory
The directory also does not appear in the source repo

https://github.com/biblepay/biblepay-evolution/tree/master/src/crypto

Finally compilation halts with the following message:
Code: [Select]
In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9971: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[2]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[2]: Leaving directory '/home/xmrbbp/biblepay-evolution/src'
Makefile:11657: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/xmrbbp/biblepay-evolution/src'
Makefile:686: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Advice would be greatly appreciated!

Thanks.
So there are a few issues here:
1) When you git clone you must clone the develop branch (not only to get the right branch, but also to get the randomx part):
for example:
cd /
mkdir biblepay-develop
cd biblepay-develop
git clone http://github.com/biblepay/biblepay-evolution
git pull origin develop

(You can also git clone develop initially, if you want, but I think you get the idea) - the pull origin develop will pull the develop branch into the evolution folder that you cloned.
Then when you build you will of course see the RandomX part.

The 2nd problem is it appears your depends directory was not compiled, (ie resulting in the chiabls error) -- please see this compile doc:
https://github.com/biblepay/biblepay-evolution/blob/develop/BuildBiblePay.txt

Notice the part about setting the environment variables, then cd to depends then make depends then cd back to making biblepay.

ChiaBLS is part of the depends build.




Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 13, 2020, 10:12:35 AM
So i tried to run xmrig-bbp miner but i just get this message  " The code execution cannot proceed because VCRUNTIME140_1.dll was not found"
I have same error:
https://github.com/biblepay/xmrig/blob/master/binaries/xmrig-bbp-win64.exe (https://github.com/biblepay/xmrig/blob/master/binaries/xmrig-bbp-win64.exe)
Using Windows 10 64-bit


Ok, so I did reproduce this on our other windows box that does not contain a development environment, and received the same error.  So the root cause of this is the c++ compile must be compiled with more switches allowing us to statically link the dependencies in (for the windows builds).

So I have updated the OP post with a new download URL:  A zip file instead.  This allows us to pack in the other dependencies also.

Please try again with the zip file version.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 13, 2020, 12:10:58 PM
I have same error:
https://github.com/biblepay/xmrig/blob/master/binaries/xmrig-bbp-win64.exe (https://github.com/biblepay/xmrig/blob/master/binaries/xmrig-bbp-win64.exe)
Using Windows 10 64-bit



Ok, so I did reproduce this on our other windows box that does not contain a development environment, and received the same error.  So the root cause of this is the c++ compile must be compiled with more switches allowing us to statically link the dependencies in (for the windows builds).

So I have updated the OP post with a new download URL:  A zip file instead.  This allows us to pack in the other dependencies also.

Please try again with the zip file version.

Cheers it works just fine now Rob!

One thing i was thinking about, is it possible to make a config.json  file  like on  normal  xmrig miner.  For the reason batch file i seem to be able to get large pages working fine but the msr mod wont work from batch file or rather trying to run batch file with admin rights wont work.

So if we could add the parameters in a config.json file can then just run the   xmrig-bbp-win64.exe with admin rights and poff we get msr  mod up and running aswell, its significant hashrate increase  perhaps 7-10% i belive. Pretty much the pool fee.

Quote
* ABOUT        XMRig/5.5.5 MSVC/2017
 * BBP + XMR - Welcome to the future of orphan charity
 * LIBS         libuv/1.31.0 OpenSSL/1.1.1c hwloc/2.1.0
 * HUGE PAGES   permission granted
 * 1GB PAGES    unavailable
 * CPU          AMD Ryzen 5 1600 Six-Core Processor (1) x64 AES
                L2:3.0 MB L3:16.0 MB 6C/12T NUMA:1
 * MEMORY       2.3/7.9 GB (29%)
 * DONATE       10%
 * ASSEMBLY     auto:ryzen
 * POOL #1      rxtest.biblepay.org:3008 algo auto
 * COMMANDS     hashrate, pause, resume
 * OPENCL       disabled
 * CUDA         disabled
[2020-02-13 18:40:24.583]  net  use pool rxtest.biblepay.org  Orphan Charity
[2020-02-13 18:40:24.584]  net  new job from rxtest.biblepay.org diff 75000 algo rx/0 height 2032833
[2020-02-13 18:40:24.585]  msr  to write MSR registers Administrator privileges required.
[2020-02-13 18:40:24.585]  rx   init dataset algo rx/0 (12 threads) seed 154eb7a21cd32a59...
[2020-02-13 18:40:24.592]  rx   allocated 2336 MB (2080+256) huge pages 100% 1168/1168 +JIT (6 ms)
[2020-02-13 18:40:28.270]  rx   dataset ready (3679 ms)
[2020-02-13 18:40:28.271]  cpu  use profile  *  (6 threads) scratchpad 2048 KB
[2020-02-13 18:40:28.376]  cpu  READY threads 6/6 (6) huge pages 100% 6/6 memory 12288 KB (105 ms)
[2020-02-13 18:40:29.849]  cpu  accepted (1/0) diff 1 BBP (0 ms)
[2020-02-13 18:40:30.273]  cpu  accepted (2/0) diff 75000 XMR (69 ms)
[2020-02-13 18:40:43.846]  cpu  accepted (3/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:05.197]  cpu  accepted (4/0) diff 75000 XMR (56 ms)
|    CPU # | AFFINITY | 10s H/s | 60s H/s | 15m H/s |
|        0 |       -1 |  1306.8 |     n/a |     n/a |
|        1 |       -1 |  1292.4 |     n/a |     n/a |
|        2 |       -1 |  1286.1 |     n/a |     n/a |
|        3 |       -1 |  1301.3 |     n/a |     n/a |
|        4 |       -1 |  1289.5 |     n/a |     n/a |
|        5 |       -1 |  1285.8 |     n/a |     n/a |
|        - |        - |  7761.9 |     n/a |     n/a |
[2020-02-13 18:41:18.325] speed 10s/60s/15m 7761.9 n/a n/a H/s max 7761.9 H/s
[2020-02-13 18:41:19.857]  cpu  accepted (5/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:24.840]  cpu  accepted (6/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:26.868]  cpu  accepted (7/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:28.288] speed 10s/60s/15m 7715.0 n/a n/a H/s max 7761.9 H/s
[2020-02-13 18:41:33.491]  cpu  accepted (8/0) diff 75000 XMR (73 ms)
[2020-02-13 18:41:36.665]  cpu  accepted (9/0) diff 75000 XMR (69 ms)
[2020-02-13 18:41:37.857]  cpu  accepted (10/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:40.000]  net  new job from rxtest.biblepay.org diff 180445 algo rx/0 height 2032834
[2020-02-13 18:41:40.846]  cpu  accepted (11/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:45.850]  cpu  accepted (12/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:46.850]  cpu  accepted (13/0) diff 1 BBP (0 ms)
[2020-02-13 18:41:53.930]  cpu  accepted (14/0) diff 1 BBP (0 ms)
[2020-02-13 18:42:06.575]  net  new job from rxtest.biblepay.org diff 225351 algo rx/0 height 2032834
[2020-02-13 18:42:28.325] speed 10s/60s/15m 7730.8 7597.8 n/a H/s max 7761.9 H/s
[2020-02-13 18:42:35.085]  cpu  accepted (15/0) diff 225351 XMR (66 ms)
[2020-02-13 18:42:37.312]  cpu  accepted (16/0) diff 225351 XMR (70 ms)
[2020-02-13 18:42:40.502]  cpu  accepted (17/0) diff 225351 XMR (71 ms)
[2020-02-13 18:42:48.861]  cpu  accepted (18/0) diff 1 BBP (0 ms)
[2020-02-13 18:42:49.661]  net  new job from rxtest.biblepay.org diff 418694 algo rx/0 height 2032835
[2020-02-13 18:42:49.860]  cpu  accepted (19/0) diff 1 BBP (0 ms)
[2020-02-13 18:42:52.308]  cpu  accepted (20/0) diff 1 BBP (0 ms)
[2020-02-13 18:42:59.878]  cpu  accepted (21/0) diff 1 BBP (0 ms)
[2020-02-13 18:43:17.850]  cpu  accepted (22/0) diff 1 BBP (0 ms)
[2020-02-13 18:43:28.345] speed 10s/60s/15m 7373.9 7095.0 n/a H/s max 7761.9 H/s
|    CPU # | AFFINITY | 10s H/s | 60s H/s | 15m H/s |
|        0 |       -1 |  1231.3 |  1190.4 |     n/a |
|        1 |       -1 |  1243.4 |  1183.2 |     n/a |
|        2 |       -1 |  1225.2 |  1177.4 |     n/a |
|        3 |       -1 |  1239.1 |  1188.7 |     n/a |
|        4 |       -1 |  1242.8 |  1178.0 |     n/a |
|        5 |       -1 |  1235.2 |  1182.4 |     n/a |
|        - |        - |  7417.0 |  7100.1 |     n/a |
[2020-02-13 18:43:32.674] speed 10s/60s/15m 7417.0 7100.1 n/a H/s max 7761.9 H/s
[2020-02-13 18:43:45.868]  cpu  accepted (23/0) diff 1 BBP (0 ms)
[2020-02-13 18:43:54.860]  cpu  accepted (24/0) diff 1 BBP (0 ms)
[2020-02-13 18:43:57.867]  cpu  accepted (25/0) diff 1 BBP (0 ms)
[2020-02-13 18:44:00.861]  cpu  accepted (26/0) diff 1 BBP (0 ms)
[2020-02-13 18:44:05.168] SIGHUP received, exiting
[2020-02-13 18:44:05.170]  cpu  stopped (1 ms)

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 13, 2020, 01:40:33 PM
Cheers it works just fine now Rob!

One thing i was thinking about, is it possible to make a config.json  file  like on  normal  xmrig miner.  For the reason batch file i seem to be able to get large pages working fine but the msr mod wont work from batch file or rather trying to run batch file with admin rights wont work.

So if we could add the parameters in a config.json file can then just run the   xmrig-bbp-win64.exe with admin rights and poff we get msr  mod up and running aswell, its significant hashrate increase  perhaps 7-10% i belive. Pretty much the pool fee.

This is great, looks like a very good start for us, that its working now on your end.

So although I'm not entirely against the config file, I feel with our modded pool requirements, it might not be in our best interests to make the config file itself work, if we can make all of the functionality work for the most part for our pool(s).  This is because the config file will be primarily used by miners who want the multipool (failover) strategies, and, I think that is something we can make available if this ecosystem actually takes off (but of course, that still requires knowledge of how our pools will work, so even the failover strategy will be customized).

However, I am all for making the advanced mods work for the miner inherently by default, to give them 98%+ of the available hashrate.

So for this first baby step, since I actually have no windows 10 boxes in my house (I did have one but it was burned last year), Id like to ask you to try an expiriment first.  I believe the MSR mod is already compiled in this version (5.5.5). 

Could you please try this:  Add the msr mod ryzen config settings to the mining batch file, then create a shortcut in windows for the command prompt, then right click it and Launch as Administrator, then launch the mining batch file?  Did that solve the problem and let the miner see that it has admin rights?

Thanks!

EDIT: On my windows 7 box, I click start, find the cmd.exe icon, then right click it and launch it as admin.  Then I run the miner from the command prompt.  But in my personal case, I cant install the Win10SDK for the msr mod because I dont have win10 to try this part on so my miner skips over the msr check.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 13, 2020, 01:50:57 PM
This is great, looks like a very good start for us, that its working now on your end.

So although I'm not entirely against the config file, I feel with our modded pool requirements, it might not be in our best interests to make the config file itself work, if we can make all of the functionality work for the most part for our pool(s).  This is because the config file will be primarily used by miners who want the multipool (failover) strategies, and, I think that is something we can make available if this ecosystem actually takes off (but of course, that still requires knowledge of how our pools will work, so even the failover strategy will be customized).

However, I am all for making the advanced mods work for the miner inherently by default, to give them 98%+ of the available hashrate.

So for this first baby step, since I actually have no windows 10 boxes in my house (I did have one but it was burned last year), Id like to ask you to try an expiriment first.  I believe the MSR mod is already compiled in this version (5.5.5). 

Could you please try this:  Add the msr mod ryzen config settings to the mining batch file, then create a shortcut in windows for the command prompt, then right click it and Launch as Administrator, then launch the mining batch file?  Did that solve the problem and let the miner see that it has admin rights?

Thanks!

EDIT: On my windows 7 box, I click start, find the cmd.exe icon, then right click it and launch it as admin.  Then I run the miner from the command prompt.  But in my personal case, I cant install the Win10SDK for the msr mod because I dont have win10 to try this part on so my miner skips over the msr check.

Wait, I think I found a way for you to make it work.
Right click on xmrig-bbp64.exe, check Run as admistrator | Save.  Now restart with the batch file, and it says on my output:  MSR  - Ryzen registers set successfully.
For me, it did not increase my HPS, but I have 30 windows open and a VM running that takes up 70% of my ram, etc.

Let me know if it actually worked?

EDIT:  It might have increased by 5%.  I need to try it after a reboot.


Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 13, 2020, 02:13:15 PM
Wait, I think I found a way for you to make it work.
Right click on xmrig-bbp64.exe, check Run as admistrator | Save.  Now restart with the batch file, and it says on my output:  MSR  - Ryzen registers set successfully.
For me, it did not increase my HPS, but I have 30 windows open and a VM running that takes up 70% of my ram, etc.

Let me know if it actually worked?

EDIT:  It might have increased by 5%.  I need to try it after a reboot.

After Reading your replies i tried various things, i found that the thing that works that i managed to get to work so far was to open up cmd as adminstrator then just cd to  path, then just copy paste parameters  from batch file and voila  the msr mod is kicking up. ;D
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 13, 2020, 02:23:43 PM
Wait, I think I found a way for you to make it work.
Right click on xmrig-bbp64.exe, check Run as admistrator | Save.  Now restart with the batch file, and it says on my output:  MSR  - Ryzen registers set successfully.
For me, it did not increase my HPS, but I have 30 windows open and a VM running that takes up 70% of my ram, etc.

Let me know if it actually worked?

EDIT:  It might have increased by 5%.  I need to try it after a reboot.

I logged latest attempt and seems pretty high hashrate jump for me gonna play abit with threads and cores for my ryzen 5 1600.

gonna try a ryzen 5 3600 and a 1920x in the coming days aswell.

Quote
* ABOUT        XMRig/5.5.5 MSVC/2017
 * BBP + XMR - Welcome to the future of orphan charity
 * LIBS         libuv/1.31.0 OpenSSL/1.1.1c hwloc/2.1.0
 * HUGE PAGES   permission granted
 * 1GB PAGES    unavailable
 * CPU          AMD Ryzen 5 1600 Six-Core Processor (1) x64 AES
                L2:3.0 MB L3:16.0 MB 6C/12T NUMA:1
 * MEMORY       2.2/7.9 GB (28%)
 * DONATE       10%
 * ASSEMBLY     auto:ryzen
 * POOL #1      rxtest.biblepay.org:3008 algo auto
 * COMMANDS     hashrate, pause, resume
 * OPENCL       disabled
 * CUDA         disabled
[2020-02-13 21:15:46.854]  net  use pool rxtest.biblepay.org  Orphan Charity
[2020-02-13 21:15:46.856]  net  new job from rxtest.biblepay.org diff 75000 algo rx/0 height 2032914
[2020-02-13 21:15:47.052]  msr  register values for "ryzen" preset has been set successfully (196 ms)
[2020-02-13 21:15:47.053]  rx   init dataset algo rx/0 (12 threads) seed 154eb7a21cd32a59...
[2020-02-13 21:15:47.060]  rx   allocated 2336 MB (2080+256) huge pages 100% 1168/1168 +JIT (6 ms)
[2020-02-13 21:15:50.381]  rx   dataset ready (3321 ms)
[2020-02-13 21:15:50.383]  cpu  use profile  *  (6 threads) scratchpad 2048 KB
[2020-02-13 21:15:50.537]  cpu  READY threads 6/6 (6) huge pages 100% 6/6 memory 12288 KB (154 ms)
[2020-02-13 21:15:52.081]  cpu  accepted (1/0) diff 1 BBP (0 ms)
[2020-02-13 21:15:52.165]  cpu  accepted (2/0) diff 75000 XMR (56 ms)
[2020-02-13 21:15:54.121]  cpu  accepted (3/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:00.145]  cpu  accepted (4/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:02.160]  cpu  accepted (5/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:08.208]  cpu  accepted (6/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:15.279]  cpu  accepted (7/0) diff 1 BBP (0 ms)
|    CPU # | AFFINITY | 10s H/s | 60s H/s | 15m H/s |
|        0 |       -1 |  1390.3 |     n/a |     n/a |
|        1 |       -1 |  1406.9 |     n/a |     n/a |
|        2 |       -1 |  1392.9 |     n/a |     n/a |
|        3 |       -1 |  1374.2 |     n/a |     n/a |
|        4 |       -1 |  1384.9 |     n/a |     n/a |
|        5 |       -1 |  1382.8 |     n/a |     n/a |
|        - |        - |  8332.0 |     n/a |     n/a |
[2020-02-13 21:16:19.286] speed 10s/60s/15m 8332.0 n/a n/a H/s max 8459.7 H/s
[2020-02-13 21:16:26.328]  cpu  accepted (8/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:33.307]  cpu  accepted (9/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:39.310]  cpu  accepted (10/0) diff 1 BBP (0 ms)
[2020-02-13 21:16:50.698] speed 10s/60s/15m 8433.9 n/a n/a H/s max 8516.0 H/s
|    CPU # | AFFINITY | 10s H/s | 60s H/s | 15m H/s |
|        0 |       -1 |  1415.0 |  1406.5 |     n/a |
|        1 |       -1 |  1414.4 |  1408.8 |     n/a |
|        2 |       -1 |  1418.1 |  1411.0 |     n/a |
|        3 |       -1 |  1417.3 |  1406.6 |     n/a |
|        4 |       -1 |  1421.9 |  1401.0 |     n/a |
|        5 |       -1 |  1425.1 |  1411.1 |     n/a |
|        - |        - |  8511.8 |  8445.1 |     n/a |
[2020-02-13 21:17:01.096] speed 10s/60s/15m 8511.8 8445.1 n/a H/s max 8523.9 H/s
[2020-02-13 21:17:04.001]  cpu  accepted (11/0) diff 75000 XMR (67 ms)
[2020-02-13 21:17:16.330]  cpu  accepted (12/0) diff 1 BBP (0 ms)
[2020-02-13 21:17:21.214]  cpu  accepted (13/0) diff 75000 XMR (61 ms)
[2020-02-13 21:17:23.853] SIGHUP received, exiting
[2020-02-13 21:17:23.856]  cpu  stopped (2 ms)

Looks like 8-10% increase for me in hashrate with the MSR mod Active.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 13, 2020, 02:37:55 PM
** MSR MOD Update **

Just a note for anyone who is attempting to add the msr mod.  I see that in the code, we already do set the registers for the ryzen for the msr mod, so I believe you do not need to install the windows10 debugging kit, or follow any of these commands listed in the below reddit thread, or add anything to your batch file.  You only need to right click on the miner.exe and check run as administrator.  The code should do the rest including setting the registers for MSR and launching the miner.

https://www.reddit.com/r/MoneroMining/comments/e9tuvd/randomx_boost_guide_for_ryzen_on_windows_9100_hs/
^^ These cpu register values are compiled in the code already ^^

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 13, 2020, 02:40:04 PM
I logged latest attempt and seems pretty high hashrate jump for me gonna play abit with threads and cores for my ryzen 5 1600.

gonna try a ryzen 5 3600 and a 1920x in the coming days aswell.

Looks like 8-10% increase for me in hashrate with the MSR mod Active.

Thats great!

Yeah, Ill post my HPS when I finally reboot.  I remember seeing about 5,000 hps when my memory is in use, but around 9,000 on a fresh reboot when the large pages are available.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: oncoapop on February 13, 2020, 04:48:29 PM
So there are a few issues here:
1) When you git clone you must clone the develop branch (not only to get the right branch, but also to get the randomx part):
for example:
cd /
mkdir biblepay-develop
cd biblepay-develop
git clone http://github.com/biblepay/biblepay-evolution
git pull origin develop

(You can also git clone develop initially, if you want, but I think you get the idea) - the pull origin develop will pull the develop branch into the evolution folder that you cloned.
Then when you build you will of course see the RandomX part.

The 2nd problem is it appears your depends directory was not compiled, (ie resulting in the chiabls error) -- please see this compile doc:
https://github.com/biblepay/biblepay-evolution/blob/develop/BuildBiblePay.txt

Notice the part about setting the environment variables, then cd to depends then make depends then cd back to making biblepay.

ChiaBLS is part of the depends build.

Yes, I do apologise. I recall that you did tell me this before and so I used the old testnet script with the new RandomX part and it completed the compile. Thank you.

For the record
Code: [Select]

cd
git clone -b develop http://github.com/biblepay/biblepay-evolution

# RandomX Part
cd biblepay-evolution/src/crypto/RandomX
mkdir build && cd build
cmake -DARCH=native ..
make
cd ../../../../..
# end of RandomX Part

evodir=$HOME"/biblepay-evolution"
cd $evodir/depends

# Build with all cores, depending on the number of CPU cores available
cores=`lscpu | grep "^CPU(s):" | awk -F" " '{print $2}'`
proc=$cores

make -j$proc

cd ..

./autogen.sh

wdir=`pwd`
./configure --prefix $wdir/depends/x86_64-pc-linux-gnu

make -j$proc

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 14, 2020, 06:54:07 AM
Have been running cense last evening the bbp-xmrig dual miner.  Theres no diffrence in wattage from just mining monero to this dual miner  from what i can tell.

Came home from part time work and i see that the miner is still running, the monero "part" of it anyway but the BBP shares stopped like 5 hours ago, ill link the log file:

Quote
[2020-02-14 10:13:38.371]  net  new job from rxtest.biblepay.org diff 214662 algo rx/0 height 2033321
[2020-02-14 10:13:55.824]  cpu  accepted (3430/0) diff 1 BBP (0 ms)
[2020-02-14 10:14:07.826]  cpu  accepted (3431/0) diff 1 BBP (0 ms)
[2020-02-14 10:14:25.820]  cpu  accepted (3432/0) diff 1 BBP (0 ms)
[2020-02-14 10:14:32.601] speed 10s/60s/15m 7695.1 7650.9 7691.6 H/s max 7711.5 H/s
[2020-02-14 10:14:38.368]  cpu  accepted (3433/0) diff 214662 XMR (69 ms)
[2020-02-14 10:14:39.848]  cpu  accepted (3434/0) diff 1 BBP (0 ms)
[2020-02-14 10:15:21.901]  net  new job from rxtest.biblepay.org diff 214812 algo rx/0 height 2033322
[2020-02-14 10:15:23.153] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 10:15:23.637]  net  orphan donations started
[2020-02-14 10:15:23.638]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033322
[2020-02-14 10:15:24.550]  cpu  accepted (3435/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:15:26.442] [rxtest.biblepay.org:3008] connect error: "connection refused"
[2020-02-14 10:15:32.607] speed 10s/60s/15m 7690.5 7694.2 7691.6 H/s max 7711.5 H/s
[2020-02-14 10:15:57.483] [rxtest.biblepay.org:3008] connect error: "connection refused"
[2020-02-14 10:16:02.188]  cpu  accepted (3436/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:16:03.410]  cpu  accepted (3437/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:16:04.070]  cpu  accepted (3438/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:16:19.388] [rxtest.biblepay.org:3008] connect error: "connection refused"
[2020-02-14 10:16:32.615] speed 10s/60s/15m 7695.1 7693.9 7691.6 H/s max 7711.5 H/s
[2020-02-14 10:17:06.718] [rxtest.biblepay.org:3008] connect error: "connection refused"
[2020-02-14 10:17:17.503]  cpu  accepted (3439/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:17:30.921]  cpu  accepted (3440/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:17:32.341]  cpu  accepted (3441/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:17:32.626] speed 10s/60s/15m 7693.3 7694.9 7691.6 H/s max 7711.5 H/s
[2020-02-14 10:18:11.042]  cpu  accepted (3442/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:18:12.902]  cpu  accepted (3443/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:18:32.634] speed 10s/60s/15m 7700.9 7694.8 7691.6 H/s max 7711.5 H/s
[2020-02-14 10:18:43.772]  cpu  accepted (3444/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 10:19:00.087]  net  new job from rxtest.biblepay.org-Charity diff 217125 algo rx/0 height 2033323
[2020-02-14 10:19:08.772]  cpu  accepted (3445/0) diff 217125 XMR-Charity (0 ms)
[2020-02-14 10:19:32.642] speed 10s/60s/15m 7690.4 7691.4 7691.3 H/s max 7711.5 H/s
[2020-02-14 10:19:57.111]  net  new job from rxtest.biblepay.org-Charity diff 235379 algo rx/0 height 2033324
[2020-02-14 10:20:09.303]  cpu  accepted (3446/0) diff 235379 XMR-Charity (0 ms)
[2020-02-14 10:20:32.651] speed 10s/60s/15m 7695.0 7694.7 7691.3 H/s max 7711.5 H/s
[2020-02-14 10:21:32.659] speed 10s/60s/15m 7694.6 7695.6 7691.4 H/s max 7711.5 H/s
[2020-02-14 10:21:51.175]  cpu  accepted (3447/0) diff 235379 XMR-Charity (0 ms)
[2020-02-14 10:22:07.082]  net  new job from rxtest.biblepay.org-Charity diff 217565 algo rx/0 height 2033325
[2020-02-14 10:22:27.227]  net  new job from rxtest.biblepay.org-Charity diff 217565 algo rx/0 height 2033326
[2020-02-14 10:22:32.666] speed 10s/60s/15m 7694.4 7695.9 7691.3 H/s max 7711.5 H/s
[2020-02-14 10:23:32.676] speed 10s/60s/15m 7693.7 7694.7 7691.5 H/s max 7711.5 H/s
[2020-02-14 10:23:48.255]  net  new job from rxtest.biblepay.org-Charity diff 177324 algo rx/0 height 2033327
[2020-02-14 10:23:49.177]  cpu  accepted (3448/0) diff 177324 XMR-Charity (0 ms)
[2020-02-14 10:24:18.863]  cpu  accepted (3449/0) diff 177324 XMR-Charity (0 ms)
[2020-02-14 10:24:28.246]  cpu  accepted (3450/0) diff 177324 XMR-Charity (0 ms)
[2020-02-14 10:24:32.687] speed 10s/60s/15m 7695.4 7694.7 7691.5 H/s max 7711.5 H/s
[2020-02-14 10:24:45.882]  net  new job from rxtest.biblepay.org-Charity diff 216251 algo rx/0 height 2033328
[2020-02-14 10:24:50.491]  cpu  accepted (3451/0) diff 216251 XMR-Charity (0 ms)
[2020-02-14 10:25:23.637]  net  orphan donations finished
[2020-02-14 10:25:23.639]  net  new job from rxtest.biblepay.org diff 212013 algo rx/0 height 2033328
[2020-02-14 10:25:32.696] speed 10s/60s/15m 7694.7 7695.6 7691.5 H/s max 7711.5 H/s
[2020-02-14 10:26:08.687]  cpu  accepted (3452/0) diff 212013 XMR (69 ms)
[2020-02-14 10:26:14.046]  cpu  accepted (3453/0) diff 212013 XMR (74 ms)
[2020-02-14 10:26:27.257]  cpu  accepted (3454/0) diff 212013 XMR (85 ms)
[2020-02-14 10:26:32.703] speed 10s/60s/15m 7696.4 7694.3 7691.6 H/s max 7711.5 H/s
[2020-02-14 10:27:32.712] speed 10s/60s/15m 7696.7 7697.6 7691.8 H/s max 7711.5 H/s
[2020-02-14 10:27:49.538]  cpu  accepted (3455/0) diff 212013 XMR (75 ms)
[2020-02-14 10:28:12.478]  cpu  accepted (3456/0) diff 212013 XMR (68 ms)
[2020-02-14 10:28:32.720] speed 10s/60s/15m 7695.1 7694.3 7691.8 H/s max 7711.5 H/s
[2020-02-14 10:28:38.489]  cpu  accepted (3457/0) diff 212013 XMR (76 ms)
[2020-02-14 10:28:43.890]  cpu  accepted (3458/0) diff 212013 XMR (55 ms)
[2020-02-14 10:28:59.409]  net  new job from rxtest.biblepay.org diff 212559 algo rx/0 height 2033329
[2020-02-14 10:29:13.468]  cpu  accepted (3459/0) diff 212559 XMR (71 ms)
[2020-02-14 10:29:24.829]  cpu  accepted (3460/0) diff 212559 XMR (71 ms)
[2020-02-14 10:29:32.730] speed 10s/60s/15m 7695.7 7693.8 7694.7 H/s max 7711.5 H/s
[2020-02-14 10:29:46.859]  net  new job from rxtest.biblepay.org diff 213107 algo rx/0 height 2033330
[2020-02-14 10:30:12.223]  cpu  accepted (3461/0) diff 213107 XMR (55 ms)
[2020-02-14 10:30:32.741] speed 10s/60s/15m 7697.4 7695.2 7694.8 H/s max 7711.5 H/s
[2020-02-14 10:30:38.240]  cpu  accepted (3462/0) diff 213107 XMR (72 ms)
[2020-02-14 10:31:32.751] speed 10s/60s/15m 7695.0 7695.5 7694.9 H/s max 7711.5 H/s
[2020-02-14 10:32:31.536]  net  new job from rxtest.biblepay.org diff 212970 algo rx/0 height 2033331
[2020-02-14 10:32:32.759] speed 10s/60s/15m 7698.3 7696.0 7695.0 H/s max 7711.5 H/s
[2020-02-14 10:32:58.995]  cpu  accepted (3463/0) diff 212970 XMR (55 ms)
[2020-02-14 10:33:32.766] speed 10s/60s/15m 7694.1 7695.8 7695.0 H/s max 7711.5 H/s
[2020-02-14 10:33:38.444]  cpu  accepted (3464/0) diff 212970 XMR (78 ms)
[2020-02-14 10:34:04.363]  cpu  accepted (3465/0) diff 212970 XMR (75 ms)
[2020-02-14 10:34:32.775] speed 10s/60s/15m 7696.3 7695.2 7695.3 H/s max 7711.5 H/s
[2020-02-14 10:35:32.785] speed 10s/60s/15m 7692.3 7682.6 7694.5 H/s max 7711.5 H/s
[2020-02-14 10:36:32.796] speed 10s/60s/15m 7692.1 7685.1 7693.8 H/s max 7711.5 H/s

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: sunk818 on February 14, 2020, 08:52:13 AM
Could you perhaps start the pool at 10k difficulty then go up? 75k is too high for my little single 4c/4t machine.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: oncoapop on February 14, 2020, 09:06:08 AM
Yes, I do apologise. I recall that you did tell me this before and so I used the old testnet script with the new RandomX part and it completed the compile. Thank you.

For the record
Code: [Select]

cd
git clone -b develop http://github.com/biblepay/biblepay-evolution

# RandomX Part
cd biblepay-evolution/src/crypto/RandomX
mkdir build && cd build
cmake -DARCH=native ..
make
cd ../../../../..
# end of RandomX Part

evodir=$HOME"/biblepay-evolution"
cd $evodir/depends

# Build with all cores, depending on the number of CPU cores available
cores=`lscpu | grep "^CPU(s):" | awk -F" " '{print $2}'`
proc=$cores

make -j$proc

cd ..

./autogen.sh

wdir=`pwd`
./configure --prefix $wdir/depends/x86_64-pc-linux-gnu

make -j$proc


Thank you, I have now got it the external and wallet set up and am mining on testnet

http://rxtest.biblepay.org/workers (BBP)
ygsYVjsR5RamCuiXyHUAoZb7nq8aM1WDUP   1   0   100%   21.47 KH

https://minexmr.com/#worker_stats (XMR pool to test)
16.67 H/s   0.00 H/s   410000   0   0   4 minutes ago   *base address*

Code: [Select]
vm.nr_hugepages = 4
1GB pages successfully enabled
 * CPU          Intel(R) Xeon(R) CPU X7560 @ 2.27GHz (2) x64 -AES
                L2:0.5 MB L3:48.0 MB 4C/4T NUMA:1
 * MEMORY       1.4/3.9 GB (37%)
 * DONATE       10%
 * ASSEMBLY     auto:none
 * POOL #1      rxtest.biblepay.org:3008 algo auto
 * COMMANDS     hashrate, pause, resume
 * OPENCL       disabled
 * CUDA         disabled
[2020-02-14 06:49:37.424]  net  use pool rxtest.biblepay.org  Orphan Charity
[2020-02-14 06:49:37.424]  net  new job from rxtest.biblepay.org diff 75000 algo rx/0 height 2033499
[2020-02-14 06:49:37.424]  rx   init dataset algo rx/0 (4 threads) seed 154eb7a21cd32a59...
[2020-02-14 06:49:37.426]  rx   allocated 2336 MB (2080+256) huge pages 0% 0/1168 +JIT (1 ms)
[2020-02-14 06:50:26.275]  rx   dataset ready (48850 ms)
[2020-02-14 06:50:26.276]  cpu  use profile  *  (2 threads) scratchpad 2048 KB
[2020-02-14 06:50:26.309]  cpu  READY threads 2/2 (2) huge pages 100% 2/2 memory 4096 KB (33 ms)
[2020-02-14 06:50:52.508]  cpu  accepted (1/0) diff 1 BBP (0 ms)
[2020-02-14 06:51:26.459] speed 10s/60s/15m 135.1 134.1 n/a H/s max 183.3 H/s
[2020-02-14 06:51:35.559]  net  new job from rxtest.biblepay.org diff 54217 algo rx/0 height 2033500
[2020-02-14 06:52:26.599] speed 10s/60s/15m 131.6 137.5 n/a H/s max 183.3 H/s
[2020-02-14 06:53:11.739] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 06:53:12.776]  net  orphan donations started
[2020-02-14 06:53:12.776]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033500
[2020-02-14 06:53:20.105]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033501
[2020-02-14 06:53:26.833] speed 10s/60s/15m 138.0 125.3 n/a H/s max 183.3 H/s
[2020-02-14 06:53:33.432]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033502
[2020-02-14 06:54:27.094] speed 10s/60s/15m 123.8 117.0 n/a H/s max 183.3 H/s
[2020-02-14 06:55:27.334] speed 10s/60s/15m 113.1 113.6 n/a H/s max 183.3 H/s
[2020-02-14 06:55:31.757] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 06:56:27.530] speed 10s/60s/15m 155.6 147.5 n/a H/s max 200.6 H/s
[2020-02-14 06:57:27.724] speed 10s/60s/15m 117.2 148.3 n/a H/s max 220.5 H/s
[2020-02-14 06:58:27.906] speed 10s/60s/15m 135.9 151.8 n/a H/s max 236.7 H/s
[2020-02-14 06:58:33.536]  net  new job from rxtest.biblepay.org-Charity diff 50000 algo rx/0 height 2033502
[2020-02-14 06:59:01.798] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 06:59:28.023] speed 10s/60s/15m 140.9 170.6 n/a H/s max 236.7 H/s
[2020-02-14 06:59:37.751]  net  new job from rxtest.biblepay.org-Charity diff 33333 algo rx/0 height 2033503

note the errors
[2020-02-14 06:55:31.757] [rxtest.biblepay.org:3008] read error: "end of file"

debug.log (tail)
Code: [Select]
2020-02-14 14:54:36 ProcessMessages(version, 141 bytes) FAILED peer=2111
2020-02-14 14:54:41 Flushed 49 addresses to peers.dat  11ms
2020-02-14 14:54:52 ProcessMessages(version, 141 bytes) FAILED peer=2112
2020-02-14 14:55:10 ProcessMessages(version, 141 bytes) FAILED peer=2113
2020-02-14 14:55:36 CMasternodeSync::NotifyHeaderTip -- pindexNew->nHeight: 28764 fInitialDownload=0
2020-02-14 14:55:36 ConnectBlock(BIBLEPAY): spork is off, skipping transaction locking checks
2020-02-14 14:55:36 UpdateTip: new best=7394ea2f327ddbd1bbbb865412bb2106a20249d63455c894351c3ed5ef0844cf height=28764 version=0x50000010 log2_work=48.51122856 tx=46915 date='2020-02-14 14:54:42' progress=0.999988 cache=11.7MiB(63827txo) evodb_cache=1.5MiB
2020-02-14 14:55:36 {PNB}: ACC  ProcessMessages(version, 141 bytes) FAILED peer=2114
2020-02-14 14:55:50 ProcessMessages(version, 141 bytes) FAILED peer=2115
2020-02-14 14:55:59 ProcessMessages(version, 141 bytes) FAILED peer=2116
2020-02-14 14:57:05 ProcessMessages(version, 141 bytes) FAILED peer=2117
2020-02-14 14:57:10 ProcessMessages(version, 141 bytes) FAILED peer=2118
2020-02-14 14:57:28 ProcessMessages(version, 141 bytes) FAILED peer=2119
2020-02-14 14:57:31 ProcessMessages(version, 141 bytes) FAILED peer=2120
2020-02-14 14:57:41 ProcessMessages(version, 141 bytes) FAILED peer=2121
2020-02-14 14:57:42 ProcessMessages(version, 141 bytes) FAILED peer=2122
2020-02-14 14:57:55 CGovernanceObject::RequestOrphanObjects -- number objects = 0
2020-02-14 14:58:00 ProcessMessages(version, 141 bytes) FAILED peer=2123
2020-02-14 14:58:00 ProcessMessages(version, 141 bytes) FAILED peer=2124
2020-02-14 14:58:01 ProcessMessages(version, 141 bytes) FAILED peer=2125
2020-02-14 14:58:12 ProcessMessages(version, 141 bytes) FAILED peer=2126
2020-02-14 14:59:02 AdvertiseLocal: advertising address 45.62.240.90:40001

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: sunk818 on February 14, 2020, 09:12:52 AM
i sent some accepted hashes but my yf address is not showing up on pool workers. is that to be expected?


http://rxtest.biblepay.org/workers (http://rxtest.biblepay.org/workers)
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 14, 2020, 09:47:13 AM
    Yeah i was getting the same error this morning but on windows10.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 14, 2020, 09:59:14 AM
Have been running cense last evening the bbp-xmrig dual miner.  Theres no diffrence in wattage from just mining monero to this dual miner  from what i can tell.

Came home from part time work and i see that the miner is still running, the monero "part" of it anyway but the BBP shares stopped like 5 hours ago, ill link the log file:

Thats great, yeah on the bbp part dropping out, I see the same behavior.  What I have discovered is I can dual mine for about 8-14 hours or so, then the monero side keeps working and the bbp side stops.  I have a feeling that something in the code has a timeout (on the bbp side in xmrig) that I need to fix. 

In the mean time, all, please just restart the miner after a few hours if the bbp drops out and you will see yourself in the pool again.

You can clearly see the problem btw on the xmrig side by looking in the console window and seeing no "BBP 1" shares solved.

But anyway I wanted to ask you the most crucial question (Im glad to hear the wattage is the same).  Could you please do a side by side baseline between pure XMR mining from their xmrig, vs biblepay dual mining using our xmrig?  That is show us your hashrate for XMR alone vs dual XMR-BBP?  Id like to see the efficiency drop % that our blakehashes take away from the total?

Thanks!

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 14, 2020, 10:01:20 AM
i sent some accepted hashes but my yf address is not showing up on pool workers. is that to be expected?


http://rxtest.biblepay.org/workers (http://rxtest.biblepay.org/workers)

Yes, its to be expected if you hash a couple and let the block go by, yes (as you probably know from experience of running nomp pool, that the round changes when blocks change).

EDIT: Btw, the nomp in its current state only registers the BBP solved shares - the XMR shares pass through to the monero side which is not exposed in the pool yet.  Im going to add metrics for that asap.  So you must also ensure the solved hashes are solving BBP shares as XMR dont register.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 14, 2020, 10:02:17 AM
    Yeah i was getting the same error this morning but on windows10.
I think you were in the pool actually, you can see in block history that you were mining for hours.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 14, 2020, 10:04:46 AM
Thank you, I have now got it the external and wallet set up and am mining on testnet

http://rxtest.biblepay.org/workers (BBP)
ygsYVjsR5RamCuiXyHUAoZb7nq8aM1WDUP   1   0   100%   21.47 KH

https://minexmr.com/#worker_stats (XMR pool to test)
16.67 H/s   0.00 H/s   410000   0   0   4 minutes ago   *base address*

Code: [Select]
vm.nr_hugepages = 4
1GB pages successfully enabled
 * CPU          Intel(R) Xeon(R) CPU X7560 @ 2.27GHz (2) x64 -AES
                L2:0.5 MB L3:48.0 MB 4C/4T NUMA:1
 * MEMORY       1.4/3.9 GB (37%)
 * DONATE       10%
 * ASSEMBLY     auto:none
 * POOL #1      rxtest.biblepay.org:3008 algo auto
 * COMMANDS     hashrate, pause, resume
 * OPENCL       disabled
 * CUDA         disabled
[2020-02-14 06:49:37.424]  net  use pool rxtest.biblepay.org  Orphan Charity
[2020-02-14 06:49:37.424]  net  new job from rxtest.biblepay.org diff 75000 algo rx/0 height 2033499
[2020-02-14 06:49:37.424]  rx   init dataset algo rx/0 (4 threads) seed 154eb7a21cd32a59...
[2020-02-14 06:49:37.426]  rx   allocated 2336 MB (2080+256) huge pages 0% 0/1168 +JIT (1 ms)
[2020-02-14 06:50:26.275]  rx   dataset ready (48850 ms)
[2020-02-14 06:50:26.276]  cpu  use profile  *  (2 threads) scratchpad 2048 KB
[2020-02-14 06:50:26.309]  cpu  READY threads 2/2 (2) huge pages 100% 2/2 memory 4096 KB (33 ms)
[2020-02-14 06:50:52.508]  cpu  accepted (1/0) diff 1 BBP (0 ms)
[2020-02-14 06:51:26.459] speed 10s/60s/15m 135.1 134.1 n/a H/s max 183.3 H/s
[2020-02-14 06:51:35.559]  net  new job from rxtest.biblepay.org diff 54217 algo rx/0 height 2033500
[2020-02-14 06:52:26.599] speed 10s/60s/15m 131.6 137.5 n/a H/s max 183.3 H/s
[2020-02-14 06:53:11.739] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 06:53:12.776]  net  orphan donations started
[2020-02-14 06:53:12.776]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033500
[2020-02-14 06:53:20.105]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033501
[2020-02-14 06:53:26.833] speed 10s/60s/15m 138.0 125.3 n/a H/s max 183.3 H/s
[2020-02-14 06:53:33.432]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033502
[2020-02-14 06:54:27.094] speed 10s/60s/15m 123.8 117.0 n/a H/s max 183.3 H/s
[2020-02-14 06:55:27.334] speed 10s/60s/15m 113.1 113.6 n/a H/s max 183.3 H/s
[2020-02-14 06:55:31.757] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 06:56:27.530] speed 10s/60s/15m 155.6 147.5 n/a H/s max 200.6 H/s
[2020-02-14 06:57:27.724] speed 10s/60s/15m 117.2 148.3 n/a H/s max 220.5 H/s
[2020-02-14 06:58:27.906] speed 10s/60s/15m 135.9 151.8 n/a H/s max 236.7 H/s
[2020-02-14 06:58:33.536]  net  new job from rxtest.biblepay.org-Charity diff 50000 algo rx/0 height 2033502
[2020-02-14 06:59:01.798] [rxtest.biblepay.org:3008] read error: "end of file"
[2020-02-14 06:59:28.023] speed 10s/60s/15m 140.9 170.6 n/a H/s max 236.7 H/s
[2020-02-14 06:59:37.751]  net  new job from rxtest.biblepay.org-Charity diff 33333 algo rx/0 height 2033503

note the errors
[2020-02-14 06:55:31.757] [rxtest.biblepay.org:3008] read error: "end of file"

debug.log (tail)
Code: [Select]
2020-02-14 14:54:36 ProcessMessages(version, 141 bytes) FAILED peer=2111
2020-02-14 14:54:41 Flushed 49 addresses to peers.dat  11ms
2020-02-14 14:54:52 ProcessMessages(version, 141 bytes) FAILED peer=2112
2020-02-14 14:55:10 ProcessMessages(version, 141 bytes) FAILED peer=2113
2020-02-14 14:55:36 CMasternodeSync::NotifyHeaderTip -- pindexNew->nHeight: 28764 fInitialDownload=0
2020-02-14 14:55:36 ConnectBlock(BIBLEPAY): spork is off, skipping transaction locking checks
2020-02-14 14:55:36 UpdateTip: new best=7394ea2f327ddbd1bbbb865412bb2106a20249d63455c894351c3ed5ef0844cf height=28764 version=0x50000010 log2_work=48.51122856 tx=46915 date='2020-02-14 14:54:42' progress=0.999988 cache=11.7MiB(63827txo) evodb_cache=1.5MiB
2020-02-14 14:55:36 {PNB}: ACC  ProcessMessages(version, 141 bytes) FAILED peer=2114
2020-02-14 14:55:50 ProcessMessages(version, 141 bytes) FAILED peer=2115
2020-02-14 14:55:59 ProcessMessages(version, 141 bytes) FAILED peer=2116
2020-02-14 14:57:05 ProcessMessages(version, 141 bytes) FAILED peer=2117
2020-02-14 14:57:10 ProcessMessages(version, 141 bytes) FAILED peer=2118
2020-02-14 14:57:28 ProcessMessages(version, 141 bytes) FAILED peer=2119
2020-02-14 14:57:31 ProcessMessages(version, 141 bytes) FAILED peer=2120
2020-02-14 14:57:41 ProcessMessages(version, 141 bytes) FAILED peer=2121
2020-02-14 14:57:42 ProcessMessages(version, 141 bytes) FAILED peer=2122
2020-02-14 14:57:55 CGovernanceObject::RequestOrphanObjects -- number objects = 0
2020-02-14 14:58:00 ProcessMessages(version, 141 bytes) FAILED peer=2123
2020-02-14 14:58:00 ProcessMessages(version, 141 bytes) FAILED peer=2124
2020-02-14 14:58:01 ProcessMessages(version, 141 bytes) FAILED peer=2125
2020-02-14 14:58:12 ProcessMessages(version, 141 bytes) FAILED peer=2126
2020-02-14 14:59:02 AdvertiseLocal: advertising address 45.62.240.90:40001

Let me know if the processMessages have gone away once you synced to the top.
The end of file error is pretty normal; that happens ocasionally and the miner recovers from it.
But Ill try to trap that today and see what the root cause is while Im looking for the timeout issue.

EDIT:
Ok I see you are synced to the top.  Ok, after I look into the xmrig timeout, I will look into my dev nodes log and see if I have the same process messages errors.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 14, 2020, 10:06:52 AM
Could you perhaps start the pool at 10k difficulty then go up? 75k is too high for my little single 4c/4t machine.
75k is the monero diff for the current block, but the actual pool difficulty is only 1 (for both XMR or BBP).
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 14, 2020, 10:08:18 AM
Thats great, yeah on the bbp part dropping out, I see the same behavior.  What I have discovered is I can dual mine for about 8-14 hours or so, then the monero side keeps working and the bbp side stops.  I have a feeling that something in the code has a timeout (on the bbp side in xmrig) that I need to fix. 

In the mean time, all, please just restart the miner after a few hours if the bbp drops out and you will see yourself in the pool again.

You can clearly see the problem btw on the xmrig side by looking in the console window and seeing no "BBP 1" shares solved.

But anyway I wanted to ask you the most crucial question (Im glad to hear the wattage is the same).  Could you please do a side by side baseline between pure XMR mining from their xmrig, vs biblepay dual mining using our xmrig?  That is show us your hashrate for XMR alone vs dual XMR-BBP?  Id like to see the efficiency drop % that our blakehashes take away from the total?

Thanks!

Sure thing i will do some comparisons in a few hours on a few diffrent cpus.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 14, 2020, 11:03:33 AM
Code: [Select]
2020-02-14 14:55:50 ProcessMessages(version, 141 bytes) FAILED peer=2115
2020-02-14 14:55:59 ProcessMessages(version, 141 bytes) FAILED peer=2116
2020-02-14 14:57:05 ProcessMessages(version, 141 bytes) FAILED peer=2117
2020-02-14 14:57:10 ProcessMessages(version, 141 bytes) FAILED peer=2118
2020-02-14 14:57:28 ProcessMessages(version, 141 bytes) FAILED peer=2119
2020-02-14 14:57:31 ProcessMessages(version, 141 bytes) FAILED peer=2120
2020-02-14 14:57:41 ProcessMessages(version, 141 bytes) FAILED peer=2121
2020-02-14 14:57:42 ProcessMessages(version, 141 bytes) FAILED peer=2122
2020-02-14 14:57:55 CGovernanceObject::RequestOrphanObjects -- number objects = 0
2020-02-14 14:58:00 ProcessMessages(version, 141 bytes) FAILED peer=2123
2020-02-14 14:58:00 ProcessMessages(version, 141 bytes) FAILED peer=2124
2020-02-14 14:58:01 ProcessMessages(version, 141 bytes) FAILED peer=2125
2020-02-14 14:58:12 ProcessMessages(version, 141 bytes) FAILED peer=2126
2020-02-14 14:59:02 AdvertiseLocal: advertising address 45.62.240.90:40001

So looking at this processMessages issue, yes, I confirm this is something new that has been introduced into the RandomX core version (develop) and all of our nodes are doing it for some reason when they send the version message.  So far it has not been affecting us actually connecting with each other but yet this is something that needs fixed.

Ill just put this on the todo list for now as my goal today is to:
- Fix the bug where we drop the bbp mining after hours in xmrig
- Expose the monero shares in the pool

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 14, 2020, 02:21:16 PM
Here comes some numbers from my part without fiddling to much with threads and affinity settings.  Large pages and MSR mod is active on all tests.

Ryzen 5 [email protected], msi b450m Gaming plus, 1.2v vcore, 12 threads, 2x4gb 2666 cl16

Ryzen 5 1600 (14nm)@3.3ghz, Asus b350 rog strix, 1,05v vcore, 6 threads, --cpu-affinity 0x555 1x8gb 3200mhz cl16

[email protected], msi x399 gaming pro carbon ac, 1,15v vcore, 16 threads --cpu-affinity 0x5D75D7, 4x4gb 3200mhz cl16

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: oncoapop on February 14, 2020, 02:26:28 PM
So looking at this processMessages issue, yes, I confirm this is something new that has been introduced into the RandomX core version (develop) and all of our nodes are doing it for some reason when they send the version message.  So far it has not been affecting us actually connecting with each other but yet this is something that needs fixed.

Ill just put this on the todo list for now as my goal today is to:
- Fix the bug where we drop the bbp mining after hours in xmrig
- Expose the monero shares in the pool

I noticed how the some cycles are donated to charity for both BBP and XMR. The donation appears to be identified by the "-Charity" to be transparent.

Code: [Select]
[2020-02-14 12:04:46.623]  net  orphan donations started
[2020-02-14 12:04:46.624]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033630
[2020-02-14 12:04:46.774]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033631
[2020-02-14 12:05:08.887]  cpu  accepted (1/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 12:05:23.498]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033632
[2020-02-14 12:05:24.817] speed 10s/60s/15m 118.2 240.9 n/a H/s max 351.7 H/s
[2020-02-14 12:05:28.819]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033633
[2020-02-14 12:06:24.977] speed 10s/60s/15m 164.8 164.5 n/a H/s max 351.7 H/s
[2020-02-14 12:07:25.180] speed 10s/60s/15m 163.5 160.8 n/a H/s max 351.7 H/s
[2020-02-14 12:08:25.328] speed 10s/60s/15m 180.7 176.4 n/a H/s max 351.7 H/s
[2020-02-14 12:09:25.543] speed 10s/60s/15m 143.6 154.2 n/a H/s max 351.7 H/s
[2020-02-14 12:10:25.847] speed 10s/60s/15m 149.0 146.0 n/a H/s max 351.7 H/s
[2020-02-14 12:10:28.868]  net  new job from rxtest.biblepay.org-Charity diff 14249 algo rx/0 height 2033633
[2020-02-14 12:11:05.134]  net  new job from rxtest.biblepay.org-Charity diff 11974 algo rx/0 height 2033634
[2020-02-14 12:11:15.687]  cpu  accepted (2/0) diff 11974 XMR-Charity (0 ms)
[2020-02-14 12:11:19.910]  net  new job from rxtest.biblepay.org-Charity diff 11974 algo rx/0 height 2033635
[2020-02-14 12:11:26.076] speed 10s/60s/15m 157.2 155.5 n/a H/s max 351.7 H/s
[2020-02-14 12:12:26.316] speed 10s/60s/15m 168.9 190.3 n/a H/s max 351.7 H/s
[2020-02-14 12:13:26.569] speed 10s/60s/15m 170.8 170.9 n/a H/s max 351.7 H/s
[2020-02-14 12:13:39.624]  net  new job from rxtest.biblepay.org-Charity diff 10000 algo rx/0 height 2033636
[2020-02-14 12:14:26.781] speed 10s/60s/15m 252.3 183.5 n/a H/s max 351.7 H/s
[2020-02-14 12:14:39.043]  net  new job from rxtest.biblepay.org-Charity diff 10000 algo rx/0 height 2033637
[2020-02-14 12:14:46.625]  net  orphan donations finished

I can see the start and end of the orphan donations and then afterward I can see that I am now mining to my wallet, I presume.

Code: [Select]
[2020-02-14 12:14:46.628]  net  new job from rxtest.biblepay.org diff 10000 algo rx/0 height 2033637
[2020-02-14 12:14:50.578]  cpu  accepted (3/0) diff 10000 XMR (91 ms)
[2020-02-14 12:14:57.340]  cpu  accepted (4/0) diff 10000 XMR (90 ms)
[2020-02-14 12:14:57.568]  cpu  accepted (5/0) diff 10000 XMR (90 ms)
[2020-02-14 12:15:01.172]  net  new job from rxtest.biblepay.org diff 10000 algo rx/0 height 2033638
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: sunk818 on February 14, 2020, 06:09:50 PM
75k is the monero diff for the current block, but the actual pool difficulty is only 1 (for both XMR or BBP).


Ok, I must have read the xmrig console text wrong then.


Initially, it took 15 minutes last night for me to get a share... then started being more consistent. So, that's what lead me to believe it was set at a high diff.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 15, 2020, 03:18:59 AM

Ok, I must have read the xmrig console text wrong then.


Initially, it took 15 minutes last night for me to get a share... then started being more consistent. So, that's what lead me to believe it was set at a high diff.

Not sure if xmrig proxy will work with this bbp-xmrig miner but it would be a way to get several low hashing rigs to be shown as 1 high performance one.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 15, 2020, 08:38:15 AM

Ok, I must have read the xmrig console text wrong then.


Initially, it took 15 minutes last night for me to get a share... then started being more consistent. So, that's what lead me to believe it was set at a high diff.

Yeah there are large swings sometimes, I solved 5 bbp for 1 randomx, then the opposite later.

I look forward to this next version will be more transparent.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 15, 2020, 08:50:00 AM
Here comes some numbers from my part without fiddling to much with threads and affinity settings.  Large pages and MSR mod is active on all tests.

Ryzen 5 [email protected], msi b450m Gaming plus, 1.2v vcore, 12 threads, 2x4gb 2666 cl16
  • Bbp+xmr=13900-14000HPS
  • 70watts (package powerdraw)
  • xmrig 5.3.0, monero hashrate = 6900-7050HPS
  • 69-70watts (package powerdraw)

Ryzen 5 1600 (14nm)@3.3ghz, Asus b350 rog strix, 1,05v vcore, 6 threads, --cpu-affinity 0x555 1x8gb 3200mhz cl16
  • Bbp+xmr= 7863-7900HPS
  • 55 watts (package powerdraw)
  • xmrig 5.3.0 , monero hashrate=3911-3950HPS
  • 55watts (package powerdraw)

[email protected], msi x399 gaming pro carbon ac, 1,15v vcore, 16 threads --cpu-affinity 0x5D75D7, 4x4gb 3200mhz cl16
  • Bbp+xmr=16100-16300HPS
  • 140-145watts (package powerdraw)
  • xmrig 5.3.0, monero hashrate= 8050-8400HPS
  • 140-145 watts (package powerdraw)


This is really excellent.

Thank you very much.

I'll put this in a spreadsheet right now, and attach it to the op post.

What this points to is a 99% efficiency level, (or truly a 198% hashpower increase without much overhead at all).  This is great, because our mission is being accomplished without any compromises.  We are not compromising blockchain security, because each solution must be based on the last block in our equation.  The miners receive two sources of income.

Its very interesting.  It appears to have the potential to be 'the cpu worlds' version of merged mining.

So yes, mining XMR alone is actually barely profitable, but the way we can look at this is our miner gets the electric bill covered from the XMR side and the BBP side is potentially pure profit.  BBP receives a revenue stream for orphan sponsorships that doesn't add sell pressure.  I feel this has the potential to take off.

Btw everyone, I spoke to Steven from SAI.ngo and he confirmed that we can sponsor Venezuelan orphans for the wholesale rate of $20.  Ill post more on that topic on the main thread.

Ok, I made a wiki page for it:
https://wiki.biblepay.org/RandomX_Hashing_Speed_Comparison

I will post it in the op.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 15, 2020, 09:34:30 AM
I noticed how the some cycles are donated to charity for both BBP and XMR. The donation appears to be identified by the "-Charity" to be transparent.

Code: [Select]
[2020-02-14 12:04:46.623]  net  orphan donations started
[2020-02-14 12:04:46.624]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033630
[2020-02-14 12:04:46.774]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033631
[2020-02-14 12:05:08.887]  cpu  accepted (1/0) diff 75000 XMR-Charity (0 ms)
[2020-02-14 12:05:23.498]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033632
[2020-02-14 12:05:24.817] speed 10s/60s/15m 118.2 240.9 n/a H/s max 351.7 H/s
[2020-02-14 12:05:28.819]  net  new job from rxtest.biblepay.org-Charity diff 75000 algo rx/0 height 2033633
[2020-02-14 12:06:24.977] speed 10s/60s/15m 164.8 164.5 n/a H/s max 351.7 H/s
[2020-02-14 12:07:25.180] speed 10s/60s/15m 163.5 160.8 n/a H/s max 351.7 H/s
[2020-02-14 12:08:25.328] speed 10s/60s/15m 180.7 176.4 n/a H/s max 351.7 H/s
[2020-02-14 12:09:25.543] speed 10s/60s/15m 143.6 154.2 n/a H/s max 351.7 H/s
[2020-02-14 12:10:25.847] speed 10s/60s/15m 149.0 146.0 n/a H/s max 351.7 H/s
[2020-02-14 12:10:28.868]  net  new job from rxtest.biblepay.org-Charity diff 14249 algo rx/0 height 2033633
[2020-02-14 12:11:05.134]  net  new job from rxtest.biblepay.org-Charity diff 11974 algo rx/0 height 2033634
[2020-02-14 12:11:15.687]  cpu  accepted (2/0) diff 11974 XMR-Charity (0 ms)
[2020-02-14 12:11:19.910]  net  new job from rxtest.biblepay.org-Charity diff 11974 algo rx/0 height 2033635
[2020-02-14 12:11:26.076] speed 10s/60s/15m 157.2 155.5 n/a H/s max 351.7 H/s
[2020-02-14 12:12:26.316] speed 10s/60s/15m 168.9 190.3 n/a H/s max 351.7 H/s
[2020-02-14 12:13:26.569] speed 10s/60s/15m 170.8 170.9 n/a H/s max 351.7 H/s
[2020-02-14 12:13:39.624]  net  new job from rxtest.biblepay.org-Charity diff 10000 algo rx/0 height 2033636
[2020-02-14 12:14:26.781] speed 10s/60s/15m 252.3 183.5 n/a H/s max 351.7 H/s
[2020-02-14 12:14:39.043]  net  new job from rxtest.biblepay.org-Charity diff 10000 algo rx/0 height 2033637
[2020-02-14 12:14:46.625]  net  orphan donations finished

I can see the start and end of the orphan donations and then afterward I can see that I am now mining to my wallet, I presume.

Code: [Select]
[2020-02-14 12:14:46.628]  net  new job from rxtest.biblepay.org diff 10000 algo rx/0 height 2033637
[2020-02-14 12:14:50.578]  cpu  accepted (3/0) diff 10000 XMR (91 ms)
[2020-02-14 12:14:57.340]  cpu  accepted (4/0) diff 10000 XMR (90 ms)
[2020-02-14 12:14:57.568]  cpu  accepted (5/0) diff 10000 XMR (90 ms)
[2020-02-14 12:15:01.172]  net  new job from rxtest.biblepay.org diff 10000 algo rx/0 height 2033638

Yes, exactly.  Over a longer period, say overnight, it should spend roughly 10% of its time donating to the pools XMR address.
I'm about to release the new pool version which computes the randomx share count and exposes it on the page also, so hopefully this will make it completely transparent.

We will also expose the pools charity address somewhere on the page, so they can click a tab and see the donations that have been mined in a given month.  I think one way we can work around Moneros anonymity features, is we can train people to look at 'the last 4 weeks of revenue mined to the XMR charity address for the pool'.  That should roughly match the monthly pool charity expenses and give a pretty close idea they are in compliance.  The script that checks the pool can work over a longer period etc.

Also, I just realized, we can make an api available to people who want to scrape the shares.  This would allow anyone to see that the pool is actually hashing 10% to orphan charity shares.  I know in the future we will need to enforce that so eventually we can release the plan that will spork-check the pools adresses, but in the launch phase, anyone can scrape the orphan share count once per hour off the pool api, and log the charity shares solved and the total pools share solved.  This should show 10% of our hashes are going to charity.

So, I think this idea is actually viable from what I can tell from a high level.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 15, 2020, 09:39:51 AM
So looking at this processMessages issue, yes, I confirm this is something new that has been introduced into the RandomX core version (develop) and all of our nodes are doing it for some reason when they send the version message.  So far it has not been affecting us actually connecting with each other but yet this is something that needs fixed.

Ill just put this on the todo list for now as my goal today is to:
- Fix the bug where we drop the bbp mining after hours in xmrig
- Expose the monero shares in the pool

Ok, thank you for reporting the processMessages issue, and also starting to recreate your sancs.  I haven't gotten around to the sancs yet (I turned off chainlocks in testnet temporarily so we can run free of sancs for a while).  But yes we can get back to that as soon as we prove RX is running reliably.

I will check out the process messages very soon - hopefully today.

In the mean time I have a new version of the pool to be released and a new miner (that adresses the shutoff bug after N hours).

Let me explain how these features work and then we can get back to checking the core client messages.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 15, 2020, 12:43:58 PM
** XMRIG 5.5.6 - Leisure Upgrade for TestNet **


Xmrig 5.5.6 is ready.  In this version we solved the issue where the bbp side mining drops out after N hours. 

Also, the rxtest pool has been upgraded.
Now you can see your XMR and BBP shares in the worker stats, and I have extended the round time to 15 minutes so we can see a clearer picture of orphan charity vs bbp mining in the worker stats.

As far as XMR transparency, we have added a new tab to the nomp pool:  XMR Inquiry.
From here you can click it and type in your XMR address and click search.  The minexmr pool will show you what you are owed on the xmr side.
To adjust your reward threshhold you can decrease it from there or request an immediate withdrawal.

So as you can see, we pass all RandomX XMR shares directly through to minexmr, hence the reason we are leveraging their website for XMR payments.

In the near future I will expose a BX link for the pools XMR charity address also - so users can click on that address and also see the BX transactions (IE what the pool generated for charity).
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 15, 2020, 02:34:13 PM
Ok, thank you for reporting the processMessages issue, and also starting to recreate your sancs.  I haven't gotten around to the sancs yet (I turned off chainlocks in testnet temporarily so we can run free of sancs for a while).  But yes we can get back to that as soon as we prove RX is running reliably.

I will check out the process messages very soon - hopefully today.

In the mean time I have a new version of the pool to be released and a new miner (that adresses the shutoff bug after N hours).

Let me explain how these features work and then we can get back to checking the core client messages.


So I debugged the processMessages (FAIL) error, and the great news is it is a harmless error and has something to do with the way we are checking the minimum peer governance version, and the message in the log is harmless.  I fixed this for the next version; but no rush in releasing it til we have a new testnet release.

I also discovered while testing your reported bug that we have an inefficiency to fix while scanning randomx headers - it turns out we can speed up the process for assessing GSCs and memorizing the prayers ; Ill let this wait also til the next release also.


Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: oncoapop on February 15, 2020, 10:21:52 PM
XMR miner on same hardware:
Code: [Select]
Model name:          Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz
Stepping:            2
CPU MHz:             1797.916
BogoMIPS:            3595.83
Virtualization:      VT-x
Hypervisor vendor:   KVM
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            30720K
NUMA node0 CPU(s):   0-5
- Compile xmrig for XMR only
Validation of hash rate from pool:
Code: [Select]
2.35 KH/s 0.00 H/s 374925243 114492 0 about a minute ago paladin
Xmrig console output:
Code: [Select]
[2020-02-15 05:48:32.798]  net  new job from us-west.minexmr.com:443 diff 117786 algo rx/0 height 2034184
[2020-02-15 05:49:05.115] speed 10s/60s/15m 2077.5 2063.7 2011.9 H/s max 2164.9 H/s
[2020-02-15 05:49:28.820]  cpu  accepted (3383/0) diff 117786 (72 ms)
[2020-02-15 05:49:32.828]  net  new job from us-west.minexmr.com:443 diff 117750 algo rx/0 height 2034185
[2020-02-15 05:50:05.168] speed 10s/60s/15m 2065.7 2054.3 2012.8 H/s max 2164.9 H/s
[2020-02-15 05:50:05.777]  net  new job from us-west.minexmr.com:443 diff 117770 algo rx/0 height 2034186
[2020-02-15 05:51:05.220] speed 10s/60s/15m 2092.0 2082.8 2018.5 H/s max 2164.9 H/s
[2020-02-15 05:51:57.700]  cpu  accepted (3384/0) diff 117770 (72 ms)
[2020-02-15 05:52:05.275] speed 10s/60s/15m 2033.7 2085.6 2025.9 H/s max 2164.9 H/s
[2020-02-15 05:52:46.657]  cpu  accepted (3385/0) diff 117770 (72 ms)
[2020-02-15 05:53:05.333] speed 10s/60s/15m 2090.6 2094.7 2033.8 H/s max 2164.9 H/s
[2020-02-15 05:53:43.143]  net  new job from us-west.minexmr.com:443 diff 117692 algo rx/0 height 2034187
[2020-02-15 05:54:05.390] speed 10s/60s/15m 2111.2 2103.9 2039.1 H/s max 2164.9 H/s
[2020-02-15 05:54:14.771]  cpu  accepted (3386/0) diff 117692 (72 ms)

Compile BBP version
>cli -version
BiblePay Core RPC client version 1.5.0.2

Compile xmrig (BBP+XMR)

Code: [Select]
* ABOUT        XMRig/5.5.6 gcc/7.4.0
 * BBP + XMR - Welcome to the future of orphan charity
 * LIBS         libuv/1.18.0 OpenSSL/1.1.1 hwloc/1.11.9
 * HUGE PAGES   supported
 * 1GB PAGES    disabled
 * CPU          Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz (6) x64 AES
                L2:0.8 MB L3:30.0 MB 6C/6T NUMA:1
 * MEMORY       8.5/15.7 GB (54%)
 * DONATE       10%
 * ASSEMBLY     auto:intel
 * POOL #1      rxtest.biblepay.org:3008 algo auto
 * COMMANDS     hashrate, pause, resume
 * OPENCL       disabled
 * CUDA         disabled
[2020-02-15 18:24:31.011]  net  use pool rxtest.biblepay.org  Orphan Charity
[2020-02-15 18:24:31.011]  net  new job from rxtest.biblepay.org diff 75000 algo rx/0 height 2034566
[2020-02-15 18:24:31.016]  msr  msr kernel module is not available

BBP pool
Biblepay
Code: [Select]
Address BBP Shares BBP Invalid XMR Shares XMR Invalid XMR Charity Shares Efficiency Hashrate
yLnVyHJxEdVVLQSmafTPsQhaeomNV96gWu 19 5 34 0 0 79.16% 102.01 KH
XMR pool
Code: [Select]
2.94 KH/s 0.00 H/s 39041199 40000 0 less than a minute ago *base address*
XMR/BBP miner console
Code: [Select]
020-02-15 19:57:54.291]  net  new job from rxtest.biblepay.org diff 120621 algo rx/0 height 2034613
[2020-02-15 19:58:01.819] speed 10s/60s/15m 4106.8 4146.3 4165.3 H/s max 4319.6 H/s
[2020-02-15 19:58:54.263]  cpu  accepted (277/20) diff 1 BBP (0 ms)
[2020-02-15 19:59:01.868] speed 10s/60s/15m 4094.9 4103.8 4156.6 H/s max 4319.6 H/s
[2020-02-15 19:59:03.058]  net  new job from rxtest.biblepay.org diff 119971 algo rx/0 height 2034614
[2020-02-15 19:59:37.747]  net  new job from rxtest.biblepay.org diff 119321 algo rx/0 height 2034615
[2020-02-15 19:59:42.731]  net  new job from rxtest.biblepay.org diff 118678 algo rx/0 height 2034616
[2020-02-15 19:59:50.170]  cpu  rejected (277/21) diff 1 BBP "Stale" (0 ms)
[2020-02-15 20:00:01.925] speed 10s/60s/15m 4018.6 4080.5 4148.4 H/s max 4319.6 H/s
[2020-02-15 20:00:11.184]  cpu  accepted (278/21) diff 1 BBP (0 ms)
[2020-02-15 20:00:32.179]  cpu  accepted (279/21) diff 1 BBP (0 ms)
[2020-02-15 20:00:35.175]  cpu  accepted (280/21) diff 1 BBP (0 ms)
[2020-02-15 20:00:56.401]  net  new job from rxtest.biblepay.org diff 117412 algo rx/0 height 2034617
[2020-02-15 20:00:58.185]  cpu  rejected (280/22) diff 1 BBP "Stale" (0 ms)
[2020-02-15 20:01:01.984] speed 10s/60s/15m 3990.0 4023.2 4136.7 H/s max 4319.6 H/s
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: sunk818 on February 15, 2020, 11:55:27 PM
I think it'd be a worthwhile experiment to see how much one would earn on a monero pool with the same hardware. Reason being is that 10% hash rate does not equal to 10% miner reward because you would need your hashes to go toward a successful monero block. What is the monero hash rate and how realistic is that bbp + xmr pool would be able to solve a monero block? the monero only pool mining would be a test to see how much would be earned from monero alone. same hardware can be pointed to bbp + xmr pool and see what results occur.


the other idea is to upstream xmr hashes to a xmr pool and get pool payments from the larger pool. when bbp + xmr pool gets large enough to contend as a pool that can hold its own, then it certainly makes sense to be its own pool.


just some random thoughts... i'm not married to either idea, just looking out for the orphans and how best to create a stable revenue stream for them.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 16, 2020, 02:42:28 AM
I think it'd be a worthwhile experiment to see how much one would earn on a monero pool with the same hardware. Reason being is that 10% hash rate does not equal to 10% miner reward because you would need your hashes to go toward a successful monero block. What is the monero hash rate and how realistic is that bbp + xmr pool would be able to solve a monero block? the monero only pool mining would be a test to see how much would be earned from monero alone. same hardware can be pointed to bbp + xmr pool and see what results occur.


the other idea is to upstream xmr hashes to a xmr pool and get pool payments from the larger pool. when bbp + xmr pool gets large enough to contend as a pool that can hold its own, then it certainly makes sense to be its own pool.


just some random thoughts... i'm not married to either idea, just looking out for the orphans and how best to create a stable revenue stream for them.

We are already mining the monero part via minexmr, one of the biggest monero pools.
And ofc its about more than just pool hashrate, ddos protection pool uptime and what not.

Another topic are you guys getting 10%  rejected stale BBP shares?

i have 2541/283 accepted bbp shares seems alot rejected ones.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 16, 2020, 09:01:57 AM
We are already mining the monero part via minexmr, one of the biggest monero pools.
And ofc its about more than just pool hashrate, ddos protection pool uptime and what not.

Another topic are you guys getting 10%  rejected stale BBP shares?

i have 2541/283 accepted bbp shares seems alot rejected ones.

So before I answer let me give a background from my perspective on the BBP rejected shares:
On version 5.5.5, I was debugging for a couple days and I noticed repetetive behavior on the xmrig side - that about after 8 hours of mining, my BBP side would drop out.  It has something to do with an expiration (which I thought I fixed in 5.5.6).  But at that time, the BBP share would be rejected in every post but it was not a stale share.

So now moving along to 5.5.6, in this version, we reconnect to the pool and reauthorize the miner automatically after a certain amount of time - and I thought that fixed it.  However it appears this actually permutated the same error into stale shares instead of connectivity issues.

So before I went to sleep last night I rebooted the pool; and this confirms that the problem is definitely inside our xmrig (not in the pool).

So for now in summary:  If you restart the xmrig miner, you can mine perfectly for about 8 hours then we start to get stale shares on every share.
I just restarted mine and now its working again.

I'll look at this today.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 16, 2020, 09:09:26 AM
XMR miner on same hardware:
Code: [Select]
Model name:          Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz
Stepping:            2
CPU MHz:             1797.916
BogoMIPS:            3595.83
Virtualization:      VT-x
Hypervisor vendor:   KVM
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            30720K
NUMA node0 CPU(s):   0-5
- Compile xmrig for XMR only
Validation of hash rate from pool:
Code: [Select]
2.35 KH/s 0.00 H/s 374925243 114492 0 about a minute ago paladin
Xmrig console output:
Code: [Select]
[2020-02-15 05:48:32.798]  net  new job from us-west.minexmr.com:443 diff 117786 algo rx/0 height 2034184
[2020-02-15 05:49:05.115] speed 10s/60s/15m 2077.5 2063.7 2011.9 H/s max 2164.9 H/s
[2020-02-15 05:49:28.820]  cpu  accepted (3383/0) diff 117786 (72 ms)
[2020-02-15 05:49:32.828]  net  new job from us-west.minexmr.com:443 diff 117750 algo rx/0 height 2034185
[2020-02-15 05:50:05.168] speed 10s/60s/15m 2065.7 2054.3 2012.8 H/s max 2164.9 H/s
[2020-02-15 05:50:05.777]  net  new job from us-west.minexmr.com:443 diff 117770 algo rx/0 height 2034186
[2020-02-15 05:51:05.220] speed 10s/60s/15m 2092.0 2082.8 2018.5 H/s max 2164.9 H/s
[2020-02-15 05:51:57.700]  cpu  accepted (3384/0) diff 117770 (72 ms)
[2020-02-15 05:52:05.275] speed 10s/60s/15m 2033.7 2085.6 2025.9 H/s max 2164.9 H/s
[2020-02-15 05:52:46.657]  cpu  accepted (3385/0) diff 117770 (72 ms)
[2020-02-15 05:53:05.333] speed 10s/60s/15m 2090.6 2094.7 2033.8 H/s max 2164.9 H/s
[2020-02-15 05:53:43.143]  net  new job from us-west.minexmr.com:443 diff 117692 algo rx/0 height 2034187
[2020-02-15 05:54:05.390] speed 10s/60s/15m 2111.2 2103.9 2039.1 H/s max 2164.9 H/s
[2020-02-15 05:54:14.771]  cpu  accepted (3386/0) diff 117692 (72 ms)

Compile BBP version
>cli -version
BiblePay Core RPC client version 1.5.0.2

Compile xmrig (BBP+XMR)

Code: [Select]
* ABOUT        XMRig/5.5.6 gcc/7.4.0
 * BBP + XMR - Welcome to the future of orphan charity
 * LIBS         libuv/1.18.0 OpenSSL/1.1.1 hwloc/1.11.9
 * HUGE PAGES   supported
 * 1GB PAGES    disabled
 * CPU          Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz (6) x64 AES
                L2:0.8 MB L3:30.0 MB 6C/6T NUMA:1
 * MEMORY       8.5/15.7 GB (54%)
 * DONATE       10%
 * ASSEMBLY     auto:intel
 * POOL #1      rxtest.biblepay.org:3008 algo auto
 * COMMANDS     hashrate, pause, resume
 * OPENCL       disabled
 * CUDA         disabled
[2020-02-15 18:24:31.011]  net  use pool rxtest.biblepay.org  Orphan Charity
[2020-02-15 18:24:31.011]  net  new job from rxtest.biblepay.org diff 75000 algo rx/0 height 2034566
[2020-02-15 18:24:31.016]  msr  msr kernel module is not available

BBP pool
Biblepay
Code: [Select]
Address BBP Shares BBP Invalid XMR Shares XMR Invalid XMR Charity Shares Efficiency Hashrate
yLnVyHJxEdVVLQSmafTPsQhaeomNV96gWu 19 5 34 0 0 79.16% 102.01 KH
XMR pool
Code: [Select]
2.94 KH/s 0.00 H/s 39041199 40000 0 less than a minute ago *base address*
XMR/BBP miner console
Code: [Select]
020-02-15 19:57:54.291]  net  new job from rxtest.biblepay.org diff 120621 algo rx/0 height 2034613
[2020-02-15 19:58:01.819] speed 10s/60s/15m 4106.8 4146.3 4165.3 H/s max 4319.6 H/s
[2020-02-15 19:58:54.263]  cpu  accepted (277/20) diff 1 BBP (0 ms)
[2020-02-15 19:59:01.868] speed 10s/60s/15m 4094.9 4103.8 4156.6 H/s max 4319.6 H/s
[2020-02-15 19:59:03.058]  net  new job from rxtest.biblepay.org diff 119971 algo rx/0 height 2034614
[2020-02-15 19:59:37.747]  net  new job from rxtest.biblepay.org diff 119321 algo rx/0 height 2034615
[2020-02-15 19:59:42.731]  net  new job from rxtest.biblepay.org diff 118678 algo rx/0 height 2034616
[2020-02-15 19:59:50.170]  cpu  rejected (277/21) diff 1 BBP "Stale" (0 ms)
[2020-02-15 20:00:01.925] speed 10s/60s/15m 4018.6 4080.5 4148.4 H/s max 4319.6 H/s
[2020-02-15 20:00:11.184]  cpu  accepted (278/21) diff 1 BBP (0 ms)
[2020-02-15 20:00:32.179]  cpu  accepted (279/21) diff 1 BBP (0 ms)
[2020-02-15 20:00:35.175]  cpu  accepted (280/21) diff 1 BBP (0 ms)
[2020-02-15 20:00:56.401]  net  new job from rxtest.biblepay.org diff 117412 algo rx/0 height 2034617
[2020-02-15 20:00:58.185]  cpu  rejected (280/22) diff 1 BBP "Stale" (0 ms)
[2020-02-15 20:01:01.984] speed 10s/60s/15m 3990.0 4023.2 4136.7 H/s max 4319.6 H/s

Thanks!
So it is very nice that your console(s) confirm that you receive 2070/4023 hps (confirming roughly 195% increase is consistent with earlz's results also) - I will add this result to the wiki page.

This also confirms that you will receive almost exactly the same XMR reward if you mine against minexmr as you would against the biblepay/xmr side.  If anyone wants to switch for a couple days feel free to as you will easily see on the minexmr earnings page the results earned.

As far as our Nomp pools hash/ps readout, I do realize that is completely wrong.  Its because no multiplier exists yet for randomx.  Ill create one asap.  I believe its just a matter of changing the multiple from 256 to something like 2.5  - (randomx hashes take a massive amount of time compared to x11 hashes - something like 2000:200000).

Edit:  Ill fix the getting started guide along with the multiplier right after we release this next bug fix.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 16, 2020, 02:09:49 PM
Ok, I updated the rxtest pool algorithm properties to be much closer to randomx.  So now the worker hashrate speed should be "closer".

Also the graph should come down to earth over the next 4 hours.

I also updated the getting started tab with the proper starting instructions.

Let me burn in the new version of xmrig before I deploy it.  If it lasts over the next 4 hours Ill preliminarily release it so we can all test it.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 17, 2020, 09:31:32 AM
Did Another comparison with 8 threads and higher Clocks.


Conclusion 10.6% increase in hashrate but 27% increase in power
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 17, 2020, 09:36:02 AM
Did Another comparison with 8 threads and higher Clocks.


Conclusion 10.6% increase in hashrate but 27% increase in Power over the 6 thread config.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 17, 2020, 09:42:36 AM
Did Another comparison with 8 threads and higher Clocks.

  • Ryzen 5 1600 (14nm)@3.3ghz, Asus b350 rog strix,  8 threads, --cpu-affinity 0xD75, 1x8gb 3200mhz cl16
  • BBP+Xmr-8740 HPS, 70 watts
  • Ryzen 5 1600 (14nm)@3.3ghz, Asus b350 rog strix,  8 threads, --cpu-affinity 0xD75, 1x8gb 3200mhz cl16
  • Xmr only - 4375HPS, 70 watts

Conclusion 10.6% increase in hashrate but 27% increase in power

Thats interesting that the 11% increase pulls 27% more watts (probably 14 more watts or so).
But it also makes me wonder about total system power consumption to break even with XMR.  I remember seeing something like 10,000 hps required to breakeven at 8 cents a kwh, but I believe I was using 500 watts for the power supply.

So out of curiosity do you know if any of these industrial miners can pack 10 ryzen procs in a single machine using some type of board, so the total system power supply is only 1500 watts?  Similar to how they chain asics together?

Im seeing that the casual gamer will pretty much receive their stipend back in the form of xmr while the household pays the electricity (plus they get bbp of course in our case which is a pro).

Im almost ready to release the new miner.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 17, 2020, 09:55:33 AM
BBP Xmrig 5.5.7e - Leisure Upgrade



Ok, this version theoretically stops the dropouts, let us please test it. 

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 17, 2020, 10:53:09 AM
Thats interesting that the 11% increase pulls 27% more watts (probably 14 more watts or so).
But it also makes me wonder about total system power consumption to break even with XMR.  I remember seeing something like 10,000 hps required to breakeven at 8 cents a kwh, but I believe I was using 500 watts for the power supply.

So out of curiosity do you know if any of these industrial miners can pack 10 ryzen procs in a single machine using some type of board, so the total system power supply is only 1500 watts?  Similar to how they chain asics together?

Im seeing that the casual gamer will pretty much receive their stipend back in the form of xmr while the household pays the electricity (plus they get bbp of course in our case which is a pro).

Im almost ready to release the new miner.



For sure its intresting idea daisy chain cpus.  Atleast i dont think there is that for ryzen processors, closest would be to get some dual socket epyc processors i belive.
Myself i just get asus boards so i can setup OS  and miner remote access and all then remove gpu and just run the machine headless.  Saves a few watts not having to think of the gpu.


something like the intel xeon phi but for ryzen would be sweet.

However we think about it its intresting years ahead with 3d stacking cpus, ddr5 coming to zen 4 i belive it was, intels forevos and so on.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 08:48:34 AM
So I'm going through the code today in an attempt to merge the latest randomx changes into xmrig, and also to harden the build to prevent crashes.
This algorithm is huge, it's a monster when considering how much machine language is generated.
I've exploited some conditions where the bytecode that is generated crashes about 10 stack frames ahead of the last hash (another words the actual crash occurs in the rx virtual machine, in machine language).  Ive been trying to isolate this as it appears to actually be in the jit code on the rx side (last night I removed all the possible biblepay code around it and it still points to the jit code, so Im merging in the latest from XMRig now to see if its something they fixed recently).

But anyway, Id like to find out each OS version that is running out there.  Im using windows 7.  Can each of you please post if you are primarily using the windows exe or the linux version?

After the next build we will need a volunteer to run the linux version for a few days straight, to ensure the jit issue is fixed.  The windows version will probably be OK, as we have a compiler flag we can  set that will overcome any machine language exceptions and let it recover (and keep mining).
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 18, 2020, 09:17:36 AM
So I'm going through the code today in an attempt to merge the latest randomx changes into xmrig, and also to harden the build to prevent crashes.
This algorithm is huge, it's a monster when considering how much machine language is generated.
I've exploited some conditions where the bytecode that is generated crashes about 10 stack frames ahead of the last hash (another words the actual crash occurs in the rx virtual machine, in machine language).  Ive been trying to isolate this as it appears to actually be in the jit code on the rx side (last night I removed all the possible biblepay code around it and it still points to the jit code, so Im merging in the latest from XMRig now to see if its something they fixed recently).

But anyway, Id like to find out each OS version that is running out there.  Im using windows 7.  Can each of you please post if you are primarily using the windows exe or the linux version?

After the next build we will need a volunteer to run the linux version for a few days straight, to ensure the jit issue is fixed.  The windows version will probably be OK, as we have a compiler flag we can  set that will overcome any machine language exceptions and let it recover (and keep mining).

Im using windows 10 on my machines.
Gonna move over my headless systems to ubuntu.  Also im no linux guru so  yeah.....

Also i have been running almost 24 hours now i belive this latest miner and it seems to me it works pretty nice.

I have  3.99%  rejected shares for bbp.
Perhaps i can get less rejected shares by changing difficulty to 256 for bbp ?

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 10:39:27 AM
Im using windows 10 on my machines.
Gonna move over my headless systems to ubuntu.  Also im no linux guru so  yeah.....

Also i have been running almost 24 hours now i belive this latest miner and it seems to me it works pretty nice.

I have  3.99%  rejected shares for bbp.
Perhaps i can get less rejected shares by changing difficulty to 256 for bbp ?
Oh ok, good to know that you have a headless linux to test on also.
Yes, please let me make a post first for the next release so you can test with the newest version as Im seeing now that monero actually doesnt recommend people to debug in MSVS as some devs are complaining about crashes, so Im building a windows version now in mingw64, to see if the problem the whole time has been the way VS2017 compiles the code.  I also see XMRig no longer supports VS.

Uh, as far as rejects, I don't think we have to worry much as let me explain something on those - and since we are such as "niche" this is actually slightly different info than POBH, or RX in prod.  Since bbp-rx solves for an algorithm, our stales mean any hash that was submitted after the block changes (or a client really was solving for the wrong prior block hash).

So, in our case our hashes will really be minimized when the difficulty increases.
Another words:  With tiny diff (we have a .005 diff in testnet), if any miners share solves the block, there is a very high propensity for stale shares over the next 30 seconds (while the clients abort the current shares and get new ones).

However, when diff is say 10 in prod, since we do support multiple solutions per round (this is in contrast to the way bbp in prod works, which will be a big pro).  Another words, you can have 20 threads running, and if 10 solve shares, they will all be accepted (because all 10 had a chance to solve that block for that round).

So basically, its more on my end - I will try increasing the pools latency for block scanning in testnet.  But in testnet, if we can get diff to increase, stale shares should drop even more to a miniscule number (ie < 1%).

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 11:08:46 AM
XMRig - 5.5.8 - Leisure Upgrade
GCC Version



This release is the GCC version for both windows and linux.
May we please test this new version on both platforms to ensure long term stability?

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 18, 2020, 11:12:19 AM
XMRig - 5.5.8 - Leisure Upgrade
GCC Version



This release is the GCC version for both windows and linux.
May we please test this new version on both platforms to ensure long term stability?

Sure thing. I will try Windows version today and tomorrow evening hopefully i will have a new rig for linux to test on aswell.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 18, 2020, 11:52:17 AM
Hey Rob.

Im testing new miner now.
Quick question, i changed the : rxtest.biblepay.org:3008 to rxtest.biblepay.org:3256

to change difficulty. Monero and charity monero seems fine from output but i havent seens any bbp solved or rejected.

Should i switch back to starting difficulty ?
Also can say that i have been running miner for 30 minutes so i figured should have gotten some bbp shares solved atleast.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 03:46:08 PM
Hey Rob.

Im testing new miner now.
Quick question, i changed the : rxtest.biblepay.org:3008 to rxtest.biblepay.org:3256

to change difficulty. Monero and charity monero seems fine from output but i havent seens any bbp solved or rejected.

Should i switch back to starting difficulty ?
Also can say that i have been running miner for 30 minutes so i figured should have gotten some bbp shares solved atleast.

Yeah, I think 256 is way too hard for randomx, let me go in and edit the pool settings and change two settings.  Just a wild guess but we might be able to get away with 2 and 5, Ill let you test those.  Theoretically the payments will work fine with the new settings - but Ill post when these are changed.

Btw, I have been debugging the GCC version now, trying to get to the source of that machine language error and I believe I finally found it.
(This Randomx algo is very interesting in that hashes have to be done in order.  Basically the problem was the original monero devs make it like this:
first hash -> next Hash -> . . . -> Test hash from a separate VM
BBP was like this:
First hash -> next Hash -> Test hash from the 'same' virtual machine.
(Sounds innoculous but the problem is it corrupts the scratchpad, and I wouldnt have known that except through this trial and error (that took about 3 days of debugging).

I just hope this is behind us!

So, I need to issue a new release.  Thanks!
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 03:58:13 PM
Hey Rob.

Im testing new miner now.
Quick question, i changed the : rxtest.biblepay.org:3008 to rxtest.biblepay.org:3256

to change difficulty. Monero and charity monero seems fine from output but i havent seens any bbp solved or rejected.

Should i switch back to starting difficulty ?
Also can say that i have been running miner for 30 minutes so i figured should have gotten some bbp shares solved atleast.

On the pool, I changed the 3 difficulties, please try these:

port 3008:  Diff = 2

Port 3032:  Diff = VarDiff (range:  1-10)

Port 3256:  Diff = 10

Thanks!

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 04:05:29 PM
XMRig - 5.5.9



Please upgrade to 5.5.9 everyone as this version has the new code to prevent out of order execution.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 18, 2020, 04:35:41 PM
5.5.9 i got up and running.
Im testing out the  3256 port.

after 5 minutes i got 2 biblepay shares so seems working better now with lower difficulty.

Positive the terminal got less cluttered. 

ill let it run 12 hours atleast.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 04:45:11 PM
5.5.9 i got up and running.
Im testing out the  3256 port.

after 5 minutes i got 2 biblepay shares so seems working better now with lower difficulty.

Positive the terminal got less cluttered. 

ill let it run 12 hours atleast.

Thanks, but unfortunately I added a new bug!

Re-releasing now (Ill increase the version).

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 04:50:44 PM
XMRig - 5.6.0


- Fix share submission bug


Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 18, 2020, 05:02:47 PM
On the pool, I changed the 3 difficulties, please try these:

port 3008:  Diff = 2

Port 3032:  Diff = VarDiff (range:  1-10)

Port 3256:  Diff = 10


I just added two more ports:


port 3008:  Diff = 2
port 3007:  Diff = 7
Port 3005:  Diff = 5
Port 3032:  Diff = VarDiff (range:  1-10)
Port 3256:  Diff = 10

Ill remove the non corresponding ports later once we work the kinks out.

EDIT:  I see we also need to pass the correct nomp difficulty through to the client (it always says 1).  Ill add to todo.


Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 19, 2020, 12:14:05 PM
Looks like this latest release was real solid! I ran one rig for over 12 hours and only a few bbp share rejects, also

Currently installed ubuntu etc on another rig and fiddling with activating 1 gb huge pages.
Then im gonna see how it works.
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 19, 2020, 02:10:10 PM
Looks like this latest release was real solid! I ran one rig for over 12 hours and only a few bbp share rejects, also

Currently installed ubuntu etc on another rig and fiddling with activating 1 gb huge pages.
Then im gonna see how it works.

Thats great!  Yeah, on an unrelated note, I probably spent 24 hours of my life doing some debugging that was unecessary.
I have been debugging xmrig in a virtual machine, and some of the changes I released were in response to believing I introduced a bug.
So just out of curiosity this morning I downloaded xmrig in the vm and ran it in debug mode and sure enough it crashed.  So the whole time Ive been dealing with something that is already part of the environment.  So basically I believe the way I need to summarize this is :  RandomX creates machine language in JIT for execution on various processors.  We cannot debug this in a vm 'normally'. 

This is pretty wild, so now I rebooted and Im testing the last version in windows again (this thing gave me so many false positives, I think after setting the MSR registers, the machine asked me to reboot, then the miner started dissapearing (silent exit) on my dev machine) - but as a strange coincinence (not related to something we added recently). 

Oh well anyway long story short it appears the GCC version is working on my windows dev machine now after a reboot, and its not exiting.

I guess I had some locked ram pages or something...

Ill try to burn this version in and confirm.

This morning I added the passthrough difficulty onto the users display.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: earlzmoade on February 19, 2020, 02:25:33 PM
Sounds nice!  8)

Yeah i was wondering before why only saw 1 difficulty  when changing bbp difficulty..

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 19, 2020, 08:37:00 PM
Pinning this for the future in case anyone else has this issue (a silent exit by the miner after a random amount of time, especially on ryzen 1700s):
https://www.reddit.com/r/MoneroMining/comments/e4k7cq/xmrig_ryzen_7_1700_fix/f9e676q/

So there is a workaround, (Im experiencing this myself), we can make a loop in a batch file like this (pretend this is miner5.bat):

:miningloop
xmrig.exe --params
goto miningloop

I will probably be doing this myself.

And just to give a little background on the problem, first of all there is a CPU setting on some motherboards called 'opcache' that might fix the underlying issue.
But the reason we aren't trying to handle this inside the program is since the JIT machine language is generated on the fly, the actual error signal is a segfault, but in a machine language area that can't have an error catch around it - and - segfaults cause program instability if you try to program around them.  Another words the only safe way to handle this is to let the process die and restart the process at the OS level.

Hopefully not many of our users will have to do this - but I appear to be one in this category with my early version of the 1700, etc. 

I havent tried the bios change yet but Ill post if it works later.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 20, 2020, 11:20:55 AM
Please all, lets remember to test English, Russian and Ukraine during the next release:

https://forum.biblepay.org/index.php?topic=494.new#new

Just ensure the English behavior of the wallet is OK, for one (IE all menus are still captioned).  And if we have any Russian speaking testers, we can use your help testing Ukraine and Russian also.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 20, 2020, 11:31:26 AM
Never mind, it looks like we will need a core wallet release anyway for a couple more reasons.

Ill try to get this ready within 24 hours.

Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 20, 2020, 07:36:04 PM
1.5.0.3-Mandatory Upgrade for TestNet


- Ensure with chainlocks disabled, we can still sync from 0
- Ensure RX performance does not impact initial sync performance
- Add mutex around multithreaded rx queries, and solve initial singlethreaded lock issue
- Merge Marcus Antonios language translations from https://forum.biblepay.org/index.php?topic=494.new#new
- Ensure VersionMessage is handled properly in this branch

** This is the windows release.  We are building the rest.  **
Title: Re: BIBLEPAY - RANDOMX INTEGRATION
Post by: Rob Andrews on February 20, 2020, 09:21:09 PM
XMRIG - 5.6.1-Leisure Upgrade for TestNet



- Pass actual share difficulty through to miner as first solved
parameter, and Solved share difficulty as second param (in brackets) for
each solved share, and add network latency to each solved share
- Modify code to be more compatible with future xmrig changes