BitShares Forum

Main => Technical Support => Topic started by: d5d on January 10, 2014, 02:52:45 am

Title: how to set up Huge page support enabled?
Post by: d5d on January 10, 2014, 02:52:45 am
centos 64
 8g
 e3 v2
cpm=230

how to set up Huge page support enabled in centos?
Title: Re: how to set up Huge page support enabled?
Post by: ripplexiaoshan on January 10, 2014, 03:10:23 pm
I think that's only for windows OS, by set lockmemoryprivilege, for Linux,it's available by default, at least It worked for me. Do you have the 1300 error?
Title: Re: how to set up Huge page support enabled?
Post by: ripplexiaoshan on January 10, 2014, 05:15:12 pm
Check "AnonHugePages" value found in /proc/meminfo

cat /proc/meminfo | grep AnonHugePages
Title: Re: how to set up Huge page support enabled?
Post by: testz on January 10, 2014, 05:16:39 pm
It's very well documented in hugepages-win64.txt and hugepages-linux64.txt which you can find inside archive.

For Windows:
Q: I am getting the following error: Error: Can not enable [SeLockMemoryPrivilege] privilege, error=1300 Warning: Huge Pages not available, performance may degrade. How can I fix that?
A: From StackOverflow http://stackoverflow.com/questions/39059/how-do-i-run-my-app-with-large-pages-in-windows

Q: I did all the above, and still getting the error=1300. What shall I do?
A: Sometimes it is needed to add "Lock pages in memory" privilege to Administrators group, your user, and run cmd.exe as Administrator. Sometimes switching off UAC helps.

Q: I am getting the following error:
Error: Can not allocate hugepages memory, error=1450
How can I fix that?
A: From MSDN ERROR_NO_SYSTEM_RESOURCES  1450 (0x5AA) Insufficient system resources exist to complete the requested service.
Ensure you have enough RAM. 8Gb of physical RAM is very strict minimum required to activate hugepages memory.
Reboot and try again. Sometimes memory fragmentation prevents from allocating enough hugepages memory.
Select smaller memory size, select less threads. If you are under virtualized environemnt, ensure both host and VM support hugepages.
Try with one thread and 512M RAM per thread.