Latest Contributions by JohnHaddad

Since streams and waterbodies don't change (relatively speaking) often, I would recommend caching them at all scales. This would take some time for the entire state, but unless there are significant changes to the underlying data, you shouldn't need to rebuild the cache anytime soon. Alternatively, you could prebuild cache tiles for the most popular areas of the state, and then set the service to build tiles on demand for the less browsed/visited areas. If you don't want to do that, then you could still use the approach that you suggest. However, you would then need to manage two services instead of one. Regardless of which approach you take, I would also look at configuring layer visibility at those smaller scales. If the data's attributes allow it, perhaps you could use definition queries to only draw major rivers and the largest water bodies at the smaller scales. Your map readers should only need to view minor streams and smaller waterbodies at the largest scales. These kinds of authoring techniques benefit dynamic map services in terms of reducing your server's load, and they also reduce the time and resources needed to build and update cached map services. Here's a list of tips and best practices: Tips and best practices for map caches—Documentation | ArcGIS Enterprise  ... View more

Hi Chad, how have you been? Pooling is a good way to reduce unnecessary RAM usage by idle services. A drawback to setting the minimum instances to 0 is that the first person to hit that service will have to wait for it to start up (after it's gone completely idle). To counter that, you can dial up the maximum time an idle instance can be kept running (although the default is pretty generous - 30 mins). With limited RAM, it's also a good idea to take a close look at the way that your services have been authored. Wherever possible, your dynamic map services should contain only the layers necessary for interactivity (queries, visualization, etc). Those services can then be used on top of cached basemaps, which use very little RAM (none if you're using online basemaps). If you publish 'all-in-one' map services with all layers being drawn dynamically, your server will use more RAM than is necessary. John ... View more

I can think of 3 possibilities: 1. Your service is cached and you are using the ArcGISDynamicMapServiceLayer directive which is for dynamic map services. 2. You are using a reverse proxy (I noticed that you are using a non-standard port) and it is not configured correctly. See http://resources.arcgis.com/content/kbase?fa=articleShow&d=32634 for more info. 3. I see a small typo in your code (space in the variable name 'basemapUR L'): { map=new esri.Map("mapDiv") var basemapURL = "http://8hXXXX:8399/arcgis/rest/services/Map_City/MapServer"; var basemap = new esri.layers.ArcGISDynamicMapServiceLayer(basemapUR L); map.addLayer(basemap);   } ... View more