How to get around working with a PA history too big for the Eclipse client max heap size (-Xmx) allowed by OS ?
![]()
We are on RTC/RRC 5.0.2 in Windows.
We are looking at using the Eclipse client to compare the Process specs at two different points in time through history of a Project Area.
Our history is so dense that we run out of heap space on the Eclipse client. We tried to increase -Xmx for more heap space, but found out that there is a limit imposed by OS. On our windows Win 7 (64 bit) we can only increase up to -Xmx1664m, otherwise the JVM cannot be created.
Is there any way to get around this? (We can always get the Process specs from the PA history on the webUI, but it does not have a compare function)
Also we wonder if our history (of process changes) is abnormally large with more than 10 changes per day, for the days we have looked at. We suspect that these changes are on addition of single (or few) custom attribute(s) to WItypes
|
2 answers
![]()
Found the solution but still no cigar. It looks like there is no limit (or pretty high we have yet to reach) for the 64-bit version of the Eclipse client (at least for 5.0.2 the one we tested): we tried up to -Xmx6G and still get a JVM created.
However our PA history (crazy there is at least 1 day with more than 48 changes during the day, if it is a 12 hrs working day it is still 4 changes an hour !!!) so dense at -Xmx5G we still did not have enough heap space, and 5G on a 8GB laptop does slow down the whole system significantly. We tried -Xmx6G but the 8GB laptop would not get anywhere.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.