GP performance in a domain, how does it scale?

Question

Active Directory

How does the number of GPOs compare to the performance of a domain controller?
50 GPs (not necessarily applied per ou), is that a lot or a little? What about 150?
Which is better in terms of performance, combine multiple policies with one setting into one object, or use the concept of one setting = one object?
Of course, we are not talking about GPs, in which there is a complex change in parameters. Those. the essence of the question is whether it is necessary to start collecting all policies with one or two parameters into one large policy in order to prevent AD performance loss

Answer 1

By no means. At least 1000+. GPO for the controller is just files lying in the domain ball. The entire application process is executed on the client, and all that is needed from the controller in the case of GPO is to be available. Grouping rules, etc. in politics - this is your personal pain. Collect everything in one or two - how will you then troubleshoot or change something? Split by 100500+ for each sneeze, you can grow a huge garden, in which you will also get lost later. Here you just need common sense, and an analysis of your specific situation and your approach is the most understandable name of the policy, and the grouping of settings is thematic. The approach to grouping rules, in fact, is similar to the grouping of computer users in AD - it’s stupid not to use groups and give access rights everywhere only to computer users,
PS Do not touch default policies AT ALL.