Sonic007 Posted April 11, 2019 Posted April 11, 2019 We've been running 12GB for domain controller and 4GB for our Sims servers. What does everyone else have? And how much do you keep for your physical host? Thanks.
LTurner3692 Posted April 11, 2019 Posted April 11, 2019 I use to have that the other way round, DC had 4GB and sims had 16GB.
FragglePete Posted April 11, 2019 Posted April 11, 2019 We've been running 12GB for domain controller and 4GB for our Sims servers. What does everyone else have? And how much do you keep for your physical host? Thanks. Surely that should be the other way around? 4Gb for DC and 12Gb for SIMS. Ours varies - also dependent on the number of vCPUs given to is. Usually start with 4Gb or 6Gb and monitor usage from there. Our SIMS has 16Gb and our DCs are on 6Gb. Pete
Norphy Posted April 11, 2019 Posted April 11, 2019 We've been running 12GB for domain controller and 4GB for our Sims servers. What does everyone else have? And how much do you keep for your physical host? Thanks. Depends entirely on the application the server is running. Anything from 4GB to 32GB. All of our virtual hosts have 256GB each.
theeggmaster Posted April 11, 2019 Posted April 11, 2019 4Gb for Domain Controllers and 16GB for SIMS. We have 192Gb in each of our two physical hosts.
Sonic007 Posted April 11, 2019 Author Posted April 11, 2019 Im redoing our Sims server at the moment and going to be having two Sims instances so two lots of databases too on the same server. Not too sure how much to allocate it.
Duke5A Posted April 11, 2019 Posted April 11, 2019 My production domain controllers have 6GB and 4GB. Each has Radius installed for wireless authentication, Google Password sync, DHCP, and one has Google Apps Directory Sync along with some scheduled tasks for automatic account creation. Both idle around 2.5GB used during operating hours.
Steve21 Posted April 11, 2019 Posted April 11, 2019 (edited) All DC's 4GB each, File Servers 6GB each (dedupe heavy setup), RDS 20GB, SIMS 20GB (again a lot of extra bits on it like Emerge etc), SCCM 24GB, and most others are between 2-4GB depending on what they are like web servers, helpdesk etc Physical host wise there's only about an 8GB balance out of 256GB per host, as it's dynamic setup so unless they are run at 100% there's always going to be "spare" over the 8GB (Assuming a full failure is in progress that is being a cluster) Steve Edited April 11, 2019 by Steve21
Sonic007 Posted April 11, 2019 Author Posted April 11, 2019 Thankyou for your replies. How many cores do you allocate? I'm currently running 4 cores for Sims and the same for DC.
Steve21 Posted April 11, 2019 Posted April 11, 2019 Depends on what each bit is running, as some servers do different bits, but generally 2 for DCs (3 DCs on-site so again roles split using failover), 2 for FileServers, 8 for SIMs (again running other software too like Emerge), Web Servers 1, others normally 2-4 depending That's based on a 64 "core" (thread) setup though, so depends how many you got to play with I guess Steve
HPlum78 Posted April 11, 2019 Posted April 11, 2019 Adding more cores is an interesting one in a VM environment as it can work against you. The service bus has to be able to allocate the resource on the host so the more cores on each VM the harder it is for the service bus to find time for allocating the required resources..... There are a lot of factors involved in sizing hosts and the VMs running on that host, contention ratio's and all that. 1
Sonic007 Posted April 12, 2019 Author Posted April 12, 2019 Thankyou, that is interesting. My new server comes with two Intel Xeon Silver 4110 2.1G, 8C/16T, 9.6GT/s , 11M Cache, Turbo. I'm a bit lost with all this multiple cores stuff. The host machine will run HyperV virtual servers, one being the domain controller and the other being a Sims server which will run two databases (two separate Sims systems). Thaknyou everyone for your help.
Steve21 Posted April 12, 2019 Posted April 12, 2019 My new server comes with two Intel Xeon Silver 4110 2.1G, 8C/16T, 9.6GT/s , 11M Cache, Turbo. Basically, to stop any issues as mentioned above you "should" limit your allocated vCPUs to your threads, so in this case 16 (8C/16T) per CPU aka 32 total if you got 2. So up to 32 vCPUs can be allocated without any contention in that regards. In reality though, over doing it by a little won't make much different (Lets say you allocate 35) unless you're expecting sub-milli responses to everything, it's only if for example you allocated 320 you're now effectively losing 90% of what you could use if that makes sense (in very simple terms before anyone abuses my maths ) Steve 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now