"Maximum memory pool" size to be more than 700MB?
It is suggested to set the "Maximum memory pool" size to be 700MB. We are facing 'Out of memory' issues when some users were "accepting changesets into repository workspaces". The processes got "cut off at around 70-80% of the process" (quotes from the user). If we increase the Max memory pool from 700MB to 1024MB, for example, could the issue be limited? Or, is it a hard limit on the size to be 700MB (I would not think so, but like to confirm)? Thanks.
|
One answer
When you say that the user reported a problem with memory, do you mean
that there was a memory problem on the server or client side? If the memory problem was on the client side, they could increase the amount of memory given to RTC/Eclipse by changing "-Xmx512m" to "-Xmx1G" in the TeamConcert.ini file. If the memory problem is happening on the server side, the memory could be increased on the server. - Matt Lavin Jazz Server Team On Thu, 2009-01-08 at 02:57 +0000, yanli wrote: It is suggested to set the "Maximum memory pool" size to be |
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.