From 3ff88ebc2e58d8adce23b6601d5fc88f0947bbbe Mon Sep 17 00:00:00 2001 From: fireice-uk Date: Fri, 6 Jan 2017 15:52:15 +0000 Subject: [PATCH] Added gpedit.msc instructions --- config.txt | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/config.txt b/config.txt index ae382bb..b70f0fa 100644 --- a/config.txt +++ b/config.txt @@ -22,6 +22,21 @@ /* * LARGE PAGE SUPPORT * 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 + * + * 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. + * + * 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. + * * 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