When setting up MapServices for ArcGIS, I'm often given an mxd that has many layers in it and told to publish it.
Should I have more mapservices with fewer layers in each, or fewer mapservices with more layers in each?
What are the tradeoffs ?
Answer
Map services are pretty costly. They require at least 1 ArcSOC process to always be running and always consuming memory (60 - 100 MB/each on my box - not exactly insignificant). Windows also has a capped Desktop Heap that can be problematic when starting lots of processes. I have frequently seen clients go down the "lets keep adding map services" route only to find out they quickly hit the top of what their server can support. Each map service would also require its own database connections which may be important to consider.
I would assume there are performance penalties with large numbers of layers in a single service as well. I don't have any information on what that is, but I can't imagine its as costly as additional map services.
No comments:
Post a Comment