I have 136 map/feature services, 5 image services, 2 system and 8 utility; plus javaw.exe (log) at 450-1000 MB & javaw.exe at ~220 MB and ArcGIS Server at 110 MB. With ArcGIS Server off - 1.65 GB, with it on 16.1 GB. All the Map/Feature/Image services are between >80 and <90 MB. I nearly choked on my coffee when I read that figure. That is a lot of services by any measure. It would be very reasonable to assume that this number of services would be consuming 15GB of memory. In terms of tweaks you could go with a more 'on-demand' approach which all of your services having a minimum number of instances set to zero. This would reduce overal memory usage as map/feature services which are not being used will 'go to sleep' and no idle ArcSOC.exe will be sitting around eating memory. Their will be a small lag upon first request of any of these services to spin up a SOC but thats a small price to pay to possibility save GBs of memory. I have a similar question as khibma, are there other reasons you need to address memory usage on this sytem? High memory usage like this is not inherently bad. The applications using memory are doing so for good reasons and are ready to respond to requests. In my experience this usage will become a problem as you choke out other services and force Windows to aggressively manage memory, such that it has to free some up for other high priority applications or OS services. Considering your base load is 75% utilization at services at idle state, it makes me worried what will happen when services started getting used and concurrent user sessions start up against those services as memory usage will increase. Is this server a dedicated host or VM? I'm asking because this approach puts you at huge risk. How many people will be affected if that one server goes offline or has a hardware failure?
... View more