RTC + Windows 32 bits + PAE
Hi guys,
We have a customer using RTC 2.0.0.2 Enterprise on Windows 2003 32bits with PAE (Physical Address Extensions).
In this case the Windows can use more than 4 GB RAM. But each process still limited to 4 GB RAM limiting the Tomcat / RTC memory.
And worse: for each case of 4GB, the windows uses 1-2 GB for the kernel, leaving the other party to the application.
So we have a server with 12 GB and the Tomcat / RTC can use about 2GB.
I think the RTC uses only one process because uses only one JVM.
But, there is a workaround to split RTC in more than one process and use more memory?
The only solution is to migrate this server to 64bit?
We have a customer using RTC 2.0.0.2 Enterprise on Windows 2003 32bits with PAE (Physical Address Extensions).
In this case the Windows can use more than 4 GB RAM. But each process still limited to 4 GB RAM limiting the Tomcat / RTC memory.
And worse: for each case of 4GB, the windows uses 1-2 GB for the kernel, leaving the other party to the application.
So we have a server with 12 GB and the Tomcat / RTC can use about 2GB.
I think the RTC uses only one process because uses only one JVM.
But, there is a workaround to split RTC in more than one process and use more memory?
The only solution is to migrate this server to 64bit?
3 answers
Hi guys,
We have a customer using RTC 2.0.0.2 Enterprise on Windows 2003 32bits with PAE (Physical Address Extensions).
In this case the Windows can use more than 4 GB RAM. But each process still limited to 4 GB RAM limiting the Tomcat / RTC memory.
And worse: for each case of 4GB, the windows uses 1-2 GB for the kernel, leaving the other party to the application.
So we have a server with 12 GB and the Tomcat / RTC can use about 2GB.
I think the RTC uses only one process because uses only one JVM.
But, there is a workaround to split RTC in more than one process and use more memory?
The only solution is to migrate this server to 64bit?
Hi Bruno
Does it perhaps help that the RTC app is running on one process (Tomcat+app), then the database is running on another process, build engine on another, etc?
If not, then your only route is a different OS that supports more memory address space.
anthony
Yes moving to 64-bit OS is your best bet. Please also see
https://jazz.net/wiki/bin/view/Main/RQMServerTuning20#Tuning_the_overall_deployment;
it's written for RQM but some of the content should also apply to RTC
On 29/05/2010 3:52 AM, bruno.braga wrote:
https://jazz.net/wiki/bin/view/Main/RQMServerTuning20#Tuning_the_overall_deployment;
it's written for RQM but some of the content should also apply to RTC
On 29/05/2010 3:52 AM, bruno.braga wrote:
Hi guys,
We have a customer using RTC 2.0.0.2 Enterprise on Windows 2003 32bits
with PAE (Physical Address Extensions).
In this case the Windows can use more than 4 GB RAM. But each process
still limited to 4 GB RAM limiting the Tomcat / RTC memory.
And worse: for each case of 4GB, the windows uses 1-2 GB for the
kernel, leaving the other party to the application.
So we have a server with 12 GB and the Tomcat / RTC can use about
2GB.
I think the RTC uses only one process because uses only one JVM.
But, there is a workaround to split RTC in more than one process and
use more memory?
The only solution is to migrate this server to 64bit?