I have been trying to do my homework when planning to eventually implement ArcGIS Enterprise but I have found limited resources finding information related to adequate hardware, infrastructure, architecture for running Enterprise. I am trying to plan for success but I having a hard time answering questions how many cores should new servers have, how much ram, etc.. I am in organization with about 75 users, probably 20 of which would possibly edit. Its really hard to say how many viewers once portal is deployed with web maps (located at a Military Base). Does anyone have any suggestions or links that might offer some assistance.
> I have been trying to do my homework when planning to eventually implement ArcGIS Enterprise but I have found limited resources finding information ...
Some good places to start:
> ... related to adequate hardware, infrastructure, architecture for running Enterprise.
This is a good resource,
Hope this helps,
Hey Spencer Larson,
Some considerations and questions I ask before I do a deployment are:
Most of my builds use the following principles:
4 Cores, 8GB RAM is a minimum for all capabilities (Note: Minimum means it will start, users will not have a very good experience using the minimum!!)
Using the above advice if I was building a test deployment of Enterprise (ArcGIS Portal, Server (Hosting), and Datastore (relational)) on a single machine I would be looking at 4 core and 24GB of RAM. For a multiple machine deployment for the same ( 3 machines with Portal, Server and Datastore on their own machine) I would look at each machine being 4 core 8GB of RAM.
Again the above machines would not deal very well with more than 5 or so users and a handful or services. I would start off with 4 core and 12GB for each service in a multi machine deployment.
I'm sure I've missed obvious things above so I'm more than happy to discuss!
If this answer was helpful please mark it as helpful. If this answer solved your question please mark it as the answer to help others who have the same question.
Hey Spencer Larson,
I would have a chat with your Esri contact as they will let you know if they can help out with this sort of work.
Depending on your level of database knowledge you may consider just using a relational data store which you will need to build when you do an enterprise build. When you publish hosted feature layers you can specify if people can edit the data which will allow people to edit the data using ArcGIS Pro or a variety of other products (Collecter, Survery123).
For your servers I would recommend you start out with one as you grow the capability in your agency and give it 32GB of RAM and 4 cores. You can always split the capabilities off on to separate machines at a later stage.
When we talk about high availability, active-active, active-passive we are talking about what happens if the server breaks. High availability generally means that you double up on everything so if one machine breaks the other one takes over. This is a more complex build and requires more administration so I would advise that you be aware of it and should you need to host mission critical data you look into it.
When we talk about balancing the load there are a few ways people interpret that. WE do multi site machines which is each machine has its own capability on it (seperate Portal, Server and Datastore onto their own machines). Multi machine generally aims to remove bottle necks and allows you to spec the machine as required for the capability. You can also balance load using two machines that are built identically and then you can share traffic between the two which helps to alleviate load.
A single machine installation will be the quickest and easiest to manage and will allow you to experience/test the capabilities that Enterprise has to offer. There are plenty of tools that you can use to monitor its usage and determine when you want to upgrade it to a more powerful machine, multi-site or load balanced. How long a single machine build will really depend on your agencies uptake of the Enterprise stack.
If you have any more questions please don't hesitate to ask!