CES 2018 is great, but a bit mind-numbing due to its size and the fact that very few major products on the server side get released during the show. I was thinking about our mining images and the fact that we have AV1 and priv (av2) images and that that seems unnecessary.
As a result, I want to make a next-gen STH Aeon Docker image that has a few features:
As a result, I want to make a next-gen STH Aeon Docker image that has a few features:
- AV1 and AV2 in a unified image
- Auto selection with manual override of AV1 or AV2
- Auto selection with manual override of number of threads
- Auto selection with manualAV1 override for the STH Aeon Pool like the current images
- Support for worker names (defaulting hostnames) for when we change software
- We found that running one instance per NUMA node is most effective. Therefore we are using --cpuset-cpus. Is this the correct behavior?
- Do we need to have an accompanying setup script and put threads/ NUMA node logic in there? For example, for all of my machines, I use a launch script which makes editing parameters for each machine extremely easy (see https://forums.servethehome.com/index.php?resources/how-to-start-mining-monero-in-docker.34/ for the Monero version)
- The flip side is that we could just make a lot of xmrig auto-configuration with numactl and such in the Docker container.
- Do we want to update to a newer (albeit slower) version of xmrig to get the API for polling workers and open up Docker ports for this?
- In a script, we could have sysctl vm.nr_hugepages=128 to ensure proper performance and other parameters.
- AV1 testing thread that shows logic when to AV1 or AV2 https://forums.servethehome.com/ind...mrig-1mb-l3-cache-docker-miner-testing.17850/
- Monero Launch Script https://forums.servethehome.com/index.php?resources/how-to-start-mining-monero-in-docker.34/