|Subject:||How much memory can I allocate to Xeams|
|Creation date:||12/14/15 4:35 PM|
|Last modified on:||8/10/18 2:11 PM|
How much memory can I allocate to Xeams?
The answer depends on how much physical memory you have on the system where Xeams is installed and which operating system are you using.
The maximum total memory on any machine equals Physical Ram
+ Virtual Memory
. Therefore, if your machine has 2 GB of physical memory and you have configured it for an additional 2 GB of virtual memory, it can use up to 4 GB for memory for all processes on the machine. However, on a 32bit platform actual memory usage cannot exceed 2 GB / process.
The following table lists memory usage for different platforms
|Platform||Suggested Maximum||Actual Maximum|
|Microsoft Windows 32 bit||512MB||1.5 GB|
|Microsoft Windows 64 bit||512MB||128 GB *|
|Linux 32 bit||512MB||1.5 GB|
|Linux 64 bit||512MB||128 GB *|
|Solaris 32 bit||512MB||3.5 GB|
|Solaris 34 bit||512MB||128 GB *|
The theoretical memory limit on a 64bit machine is about 264
, which is about 17.2 billion gigabytes. If your server requires that much of memory, you must be working for the Department of Defense.
Steps to increase memory
The following steps demonstrate how to increase memory in Xeams.
- Login in as admin to the Admin Console
- Click Configure under Memory Status
- Specify new value on the following page
Posted by Reto Botta on 2/25/16 5:03 AM
In the Xeams config directory, change the setting on the java command line, then restart Xeams.
Worked for me
Posted by marios on 5/8/16 7:40 AM
change the value direclty via service.properties on the config file and rather if it show's up that the change are made or not it will work.
Posted by Joe Weirather on 8/17/16 6:18 PM
I was able to piece together the following solution from logs and the other comments mentioned here (thank you all).
As of build 5832 (and apparently going back further), this setting is found in run.sh. In my case, the file can be found at:
Again, in my case, line 10 reads:
jre/bin/java -server -Xmx1536m -cp $CP -DLoggingConfigFile=logconfig.xml com.synametrics.xeams.ServerStarter &
The memory setting is the argument "-Xmx1536m", where the "1536" is an integer value in megabytes to allocate to the java server. In my case, I updated this number from 512 to 1536 (1.5GB), then rebooted the server (for good measure). Upon restart my memory allocation was 1.5GB, and this was also reflected in the UI/Dashboard.
For the record, the issue I was experiencing was that periodically, say every 5-10 days, the Xeams server would become completely unresponsive and remain that way. I was able to login to the physical server through SSH and Webmin, and everything seemed fine, but Xeams would not respond to any SMTP or HTTP requests. After monitoring the server using HTOP for a few days, I saw that memory was very frequently pushing the limits at 512MB, and I made the assumption that Xeams was running out of memory frequently and unable to restart. My hope is that updating the memory to 1.5GB will alleviate some or all of this.
Posted by Reto Botta on 2/25/16 5:04 AM
Sorry, forgot the most important thing:
The file you need to modify is
in the Xeams config directory
Posted by Randy Henderson on 2/27/16 9:11 PM
Roger, from the main dashboard click on the gear in the upper right corner of the Memory Status box
Posted by Roger Stumbaugh on 1/7/16 12:19 PM
This method does not work. The picture isn't even correct anymore. So has anyone ever successfully changed the memory size?
Add a comment to this document
Do you have a helpful tip related to this document that you'd like to share
with other users? Please add it below. Your name and tip will appear at the
end of the document text.