Mark
Knight
Paging hurts performance, and with a system with 512MB of physical memory I would recommend a 512MB paging file as a good starting point. Ideally, if this did not meet the needs of your server you would add more physical memory, but if that is not an option you could try extending your paging file to 1GB (keep in mind a static paging size is faster, don't let Windows dynamically set paging size).
With servers with 1GB of physical memory, you could try disabling paging completely for maximum performance, and if your server started running out of resources you could step this up to 512MB. If with 1GB physical memory and 512MB paging you still see your server running out of resources, you will want to increase your paging file to 1GB and apply the 3GB user addressing tweak. This will allow .NET, and therefore RunUO, to use the maximum amount of virtual memory possible.
With 2GB of physical memory, the 3GB tweak is a must, and both 512MB and 1GB are viable options for paging file size. Obviously in this situation there is no point increasing the paging file over 2GB, as you would go over the 4GB address limit.
I just wish everyone wasn't so quick to point the blame at RunUO's coding before they knew exactly what they were talking about.
With servers with 1GB of physical memory, you could try disabling paging completely for maximum performance, and if your server started running out of resources you could step this up to 512MB. If with 1GB physical memory and 512MB paging you still see your server running out of resources, you will want to increase your paging file to 1GB and apply the 3GB user addressing tweak. This will allow .NET, and therefore RunUO, to use the maximum amount of virtual memory possible.
With 2GB of physical memory, the 3GB tweak is a must, and both 512MB and 1GB are viable options for paging file size. Obviously in this situation there is no point increasing the paging file over 2GB, as you would go over the 4GB address limit.
I just wish everyone wasn't so quick to point the blame at RunUO's coding before they knew exactly what they were talking about.