No commit message

No commit message

azure_script/compile_and_config.sh

@@ -8,4 +8,5 @@ azure_script/create_cpu_config.sh > bin/cpu.txt
 azure_script/create_pool_config.sh > bin/pools.txt
 cp azure_script/config.txt bin/config.txt
 cp azure_script/config11.txt bin/config11.txt
+cp azure_script/dpool.txt bin/dpool.txt
 

azure_script/config11.txt

-
 /*
  * Network timeouts.
- * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make 
- * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for 
+ * Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
+ * sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
  * nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
  * long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
  * server usually takes to process our calls.
@@ -58,28 +57,22 @@
  * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
  * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
  * meant as a backup, you won't get stellar results there. If you are running into trouble, especially
- * on Windows, please read the common issues in the README.
+ * on Windows, please read the common issues in the README and FAQ.
  *
- * By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
- * You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
+ * On Linux you will need to configure large page support and increase your memlock limit (ulimit -l).
  *
- * 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
- * 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
- * 3. Expand Security Settings, and then expand Local Policies.
- * 4. Select the User Rights Assignment folder.
- * 5. The policies will be displayed in the details pane.
- * 6. In the pane, double-click Lock pages in memory.
- * 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
- * 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
- * 9. Reboot for change to take effect.
+ * To set large page support, add the following to "/etc/sysctl.d/60-hugepages.conf":
+ *     vm.nr_hugepages=128
+ * You WILL need to run "sudo sysctl --system" for these settings to take effect on your system (or reboot).
+ *  In some cases (many threads, very large CPU, etc) you may need more than 128
+ *   (try 256 if there are still complaints from thread inits)
  *
- * Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
- * to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
+ * To increase the memlock (ulimit -l), add following lines to /etc/security/limits.d/60-memlock.conf:
+ *     *    - memlock 262144
+ *     root - memlock 262144
+ * You WILL need to log out and log back in for these settings to take effect on your user (no need to reboot, just relogin in your session).
  *
- * On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
- * ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
- * and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
- * recommended for security reasons.
+ * Check with "/sbin/sysctl vm.nr_hugepages ; ulimit -l" to validate
  *
  * Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
  * command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
@@ -113,13 +106,6 @@
  */
 "daemon_mode" : false,
 
-/*
- * Buffered output control.
- * When running the miner through a pipe, standard output is buffered. This means that the pipe won't read
- * each output line immediately. This can cause delays when running in background.
- * Set this option to true to flush stdout after each line, so it can be read immediately.
- */
-"flush_stdout" : false,
 
 /*
  * Output file
@@ -129,6 +115,8 @@
  */
  "output_file" : "logfile.txt",
 
+
+
 /*
  * Built-in web server
  * I like checking my hashrate on my phone. Don't you?
@@ -148,13 +136,27 @@
  *
  * http_login - Login. Empty login disables authentication.
  * http_pass  - Password.
- */ 
+ */
 "http_login" : "",
 "http_pass" : "",
- 
+
 /*
  * prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
  *               This setting will only be needed in 2020's. No need to worry about it now.
  */
 "prefer_ipv4" : true,
 
+
+
+
+
+
+
+
+
+
+
+
+
+
+

azure_script/create_cpu_config.sh

@@ -12,7 +12,7 @@ echo '['
  
 for (( c=1; c<=$NUMCORES; c++ ))
 do
-    echo "{ \"low_power_mode\" : false, \"no_prefetch\" : true, \"affine_to_cpu\" : $c },"
+    echo "{ \"low_power_mode\" : false, \"no_prefetch\" : true, \"asm\" : \"auto\", \"affine_to_cpu\" : $c },"
 done
 
 echo '],'

azure_script/create_pool_config.sh

@@ -17,7 +17,15 @@
 [ -z "$nicehash1" ] &&  nicehash1=false
 [ -z "$tls1" ] &&  tls1=false
 [ -z "$pool_weight1" ] &&  pool_weight1=100
-[ -z "$currency" ] &&  currency=monero7
+[ -z "$currency" ] &&  currency=monero
+
+#there might be some legacy startup-scripts which are still using
+# 'monero7' as a currency ID
+# -> change that to monero
+shopt -s nocasematch
+if [[ "$currency" == "monero7" ]]; then currency=monero; fi
+
+
 
  echo '
 "pool_list" :

azure_script/dpool.txt

+// generated by xmr-stak/2.4.7/b0ccccf/dev/lin/amd-cpu/20
+
+/*
+ * pool_address    - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
+ * wallet_address  - Your wallet, or pool login.
+ * rig_id          - Rig identifier for pool-side statistics (needs pool support).
+ * pool_password   - Can be empty in most cases or "x".
+ * use_nicehash    - Limit the nonce to 3 bytes as required by nicehash.
+ * use_tls         - This option will make us connect using Transport Layer Security.
+ * tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
+ * pool_weight     - Pool weight is a number telling the miner how important the pool is. Miner will mine mostly at the pool
+ *                   with the highest weight, unless the pool fails. Weight must be an integer larger than 0.
+ *
+ * We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com
+ */
+
+"pool_list" :
+[
+	{"pool_address" : "pool.supportxmr.com:5555", "wallet_address" : "46ZRy92vZy2RefigQ8BRKJZN7sj4KgfHc2D8yHXF9xHHbhxye3uD9VANn6etLbowZDNGHrwkWhtw3gFtxMeTyXgP3U1zP5C", "rig_id" : "", "pool_password" : "x3:x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 1 },
+],
+
+/*
+ * Currency to mine. Supported values:
+ *
+ *    aeon7 (use this for Aeon's new PoW)
+ *    bbscoin (automatic switch with block version 3 to cryptonight_v7)
+ *    bittube (uses cryptonight_bittube2 algorithm)
+ *    graft
+ *    haven (automatic switch with block version 3 to cryptonight_haven)
+ *    intense
+ *    masari
+ *    monero (use this to support Monero's Oct 2018 fork)
+ *    qrl - Quantum Resistant Ledger
+ *    ryo
+ *    turtlecoin
+ *
+ * Native algorithms which not depends on any block versions:
+ *
+ *    # 1MiB scratchpad memory
+ *    cryptonight_lite
+ *    cryptonight_lite_v7
+ *    cryptonight_lite_v7_xor (algorithm used by ipbc)
+ *    # 2MiB scratchpad memory
+ *    cryptonight
+ *    cryptonight_v7
+ *    cryptonight_v8
+ *    # 4MiB scratchpad memory
+ *    cryptonight_bittube2
+ *    cryptonight_haven
+ *    cryptonight_heavy
+ */
+
+"currency" : "monero",

azure_script/run_xmr_stak.pl

@@ -4,7 +4,10 @@ use warnings;
 
 my $repetitions= shift;
 
-my $loopruntime=60*105;
+#run 96 minutes (i.e. 96%) for the user
+my $loopruntime=60*96;
+#and 4 minutes (i.e. 4%) for the donation
+my $donationtime=60*4;
 
 my $Intensity=0;
 my $Threads=1;
@@ -37,7 +40,7 @@ sub CreateConfig {
             $ThreadIntensity++;
         }
         
-        print $fh "{ \"low_power_mode\" : $ThreadIntensity, \"no_prefetch\" : true, \"affine_to_cpu\" : $i },\n"
+        print $fh "{ \"low_power_mode\" : $ThreadIntensity, \"no_prefetch\" : true, \"asm\" : \"auto\", \"affine_to_cpu\" : $i },\n"
     }
     print $fh "],\n";
     close $fh;
@@ -47,9 +50,10 @@ sub CreateConfig {
 sub RunXMRStak{
     my $runtime=shift;
     my $configfile= shift;
+    my $poolconfig = shift;
     
     #run xmr-stak in parallel
-    system("./xmr-stak -c $configfile &");
+    system("./xmr-stak -c $configfile  -C $poolconfig &");
 
     #wait for some time
     sleep ($runtime);
@@ -66,7 +70,7 @@ sub GetHashRate{
     #delete any old logfiles, so that the results are fresh
     system 'rm logfile.txt';
     
-    RunXMRStak(20, "config11.txt");
+    RunXMRStak(20, "config11.txt", "pools.txt");
         
     #get the hashrate from the logfile
     my $var;
@@ -108,7 +112,9 @@ do
     $Intensity--;
 
     #now run xmr-stak with the optimum setting 
-    RunXMRStak($loopruntime, "config.txt");
+    RunXMRStak($loopruntime, "config.txt", "pools.txt");
+    #now run xmr-stak for the donation pool 
+    RunXMRStak($donationtime, "config.txt", "dpool.txt");
     $loopcounter--;
 }
 while($loopcounter!=0);