Latest Contributions by JoshuaBixby

Part of the reason Esri has moved away from documenting single-service recommendations like the old "n+1" limit is that any such recommendation is so generic that it isn't really applicable, or at least isn't really helpful.  Unless your ArcGIS Server site only has a single service published, which I doubt very few do, how a single service is tuned really depends on all the services on the machine.  A rule like "n+1" may be a reasonable suggestion in a vacuum, but what if you have published many heavily-used services and tuned them all the same way?  It won't be pretty for any of the services when the machine is maxing out its CPU (and likely memory as well) because many heavily used services all have "n+1" max instances. Tuning an ArcGIS Server site has so many factors to consider that it is hard for single, simple suggestion to be made.  Unless you are trying to maximize or optimize computing resources too eek every last penny out of some capital expense or monthly hosting bill, at the end of the day the most basic metric of whether a service is tuned well enough is whether you are getting complaints from users.  Start with the defaults Esri provides and see what feedback you get from users. ... View more

It is an implementation artifact, not an actual desktop license or feature type.  You can think of it loosely as the license for the license manager itself, but even that isn't exactly correct. ... View more