Hello,
Sometimes some of our Vault users that use the integrated soure control in Visual Studio get the following message:
"Server Unavailable
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note:
An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur."
At the same time the following message is written in the application event log:
"aspnet_wp.exe (PID: 3780) was recycled because memory consumption exceeded the 613 MB (60 percent of available RAM)."
How can we prevent this from happening?
Regards,
Frans
"Server unavailable" in Visual Studio
Moderator: SourceGear
Frans:
A couple of different suggestions:
1) You can control the memory limit in IIS by looking at the memoryLimit attribute of the processModel XML element in the .Net's machine.config file found in the %WINDIR%\Microsoft.NET\Framework\<VERSION>\CONFIG\ directory. You may want to see if the server's tree manager will hold if 80 or 85 is used.
2) We've made some improvement in overall memory usage in Vault 3.1 Beta. If you do not use the Beta server (which is solid in our testing environment), you may want to watch for the Vault 3.1 release.
3) If you have large, large trees, try setting the TreeManagerSize element (found vault.config) to something like 50-60. You will need to restart IIS to place this change into affect.
4) Finally, if there are empty slots within your Vault server, you may want to throw in some more memory. (But that's the easy way out :>))
A couple of different suggestions:
1) You can control the memory limit in IIS by looking at the memoryLimit attribute of the processModel XML element in the .Net's machine.config file found in the %WINDIR%\Microsoft.NET\Framework\<VERSION>\CONFIG\ directory. You may want to see if the server's tree manager will hold if 80 or 85 is used.
2) We've made some improvement in overall memory usage in Vault 3.1 Beta. If you do not use the Beta server (which is solid in our testing environment), you may want to watch for the Vault 3.1 release.
3) If you have large, large trees, try setting the TreeManagerSize element (found vault.config) to something like 50-60. You will need to restart IIS to place this change into affect.
4) Finally, if there are empty slots within your Vault server, you may want to throw in some more memory. (But that's the easy way out :>))
Jeff Clausius
SourceGear
SourceGear
Jeff,
Thank you for your suggestions. I have just requested extra memory from our system administrator, apart from solving this particular problem it might help to let Vault run a bit smoother altogether if I understand correctly, because the memory is used for caching trees.
If the extra memory does notcome through soon I will try your other suggestions.
Greetings,
Frans
Thank you for your suggestions. I have just requested extra memory from our system administrator, apart from solving this particular problem it might help to let Vault run a bit smoother altogether if I understand correctly, because the memory is used for caching trees.
If the extra memory does notcome through soon I will try your other suggestions.
Greetings,
Frans
Frans:
if your repository tree is over 250,000 items, you may want to keep the server from caching too many trees.
The default value (-1), calculates a tree size based on the amount of memory found in the system. Setting this is a known value will keep the server's memory allocation in-check.
if your repository tree is over 250,000 items, you may want to keep the server from caching too many trees.
The default value (-1), calculates a tree size based on the amount of memory found in the system. Setting this is a known value will keep the server's memory allocation in-check.
Jeff Clausius
SourceGear
SourceGear