It is currently Mon Sep 16, 2019 4:32 am




 Page 1 of 1 [ 2 posts ] 
Author Message
 Post subject: Increasing memory heap size for the ChatBlazer server
PostPosted: Sat Apr 23, 2011 11:19 am 
Support Staff

Joined: Fri Nov 01, 2002 4:06 am
Posts: 43
The default memory heap size setting for the ChatBlazer server is 512MB. While this may be sufficient for most installations, some situations may require more, e.g. loading room history for many rooms. The settings below show you how to increase the heap size, depending on your environment.

Look for these lines in the respective files.

Windows service, wrapper.conf:
wrapper.java.maxmemory=1024


Linux, cb8svr.sh:
VMARGS="-Xmx1024M -server"


The examples above increase the heap size to 1GB. You can allocate more, up to a Java VM limit of 2GB.



_________________
Samuel
ChatBlazer Support
Offline
 Profile  
 
 Post subject: Re: Increasing memory heap size for the ChatBlazer server
PostPosted: Mon Apr 25, 2011 12:50 am 
New User

Joined: Sun Oct 05, 2008 9:25 pm
Posts: 16
Extract from Java Tuning (http://java.sun.com/performance/referen ... uning.html)

Quote:
The maximum heap size of a Java application is limited by three factors: the process data model (32-bit or 64-bit) and the associated operating system limitations, the amount of virtual memory available on the system, and the amount of physical memory available on the system. The size of the Java heap for a particular application can never exceed or even reach the maximum virtual address space of the process data model. For a 32-bit process model, the maximum virtual address size of the process is typically 4 GB, though some operating systems limit this to 2 GB or 3 GB. The maximum heap size is typically -Xmx3800m (1600m) for 2 GB limits), though the actual limitation is application dependent. For 64-bit process models, the maximum is essentially unlimited. For a single Java application on a dedicated system, the size of the Java heap should never be set to the amount of physical RAM on the system, as additional RAM is needed for the operating system, other system processes, and even for other JVM operations. Committing too much of a system's physical memory is likely to result in paging of virtual memory to disk, quite likely during garbage collection operations, leading to significant performance issues. On systems with multiple Java processes, or multiple processes in general, the sum of the Java heaps for those processes should also not exceed the the size of the physical RAM in the system.


Offline
 Profile  
 
Display posts from previous:  Sort by  
 Page 1 of 1 [ 2 posts ] 


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

cron