Controller (SaaS, On Premise)

cancel
Showing results for 
Search instead for 
Did you mean: 

Determine Controller host hardware size for non-production environment

SOLVED

Determine Controller host hardware size for non-production environment

We need to install an AppDynamic Controller (.net 64 Windows, on premise installer) on a dev server in a developer environment. I image there will be less than 1K request/minute most of the time. The server is for developer use. Slowness in using Controller UI is ok. Thus, we need to determine the minimal hardware requirement that can support maximum applications.

 

I have three questions below related to the radio options on the screenshot below shown up during installation.

 

1 What is application in "at most 2 applications"? I understand nodes as in  Controller System Requirements. However, application is not mentioned on the link.

6.PNG

 

2 Combined the screenshot above and the table below, If Demo is chosen, can more than 5 nodes be monitored? That is, is there a hard limit imposed on the number of nodes being monitored? We want to use lowest hardware spec, and have low request rate (e.g. <1K request/min) for apps monitored.

 

 

3. If Small is chosen, can AppDynamics be installed on a server that has 4 cores 8 GB RAM?

Installer Performance Profile

Maximum Metric Count/Minute Estimated Max Number of Nodes

Minimum Hardware Profile

Supported OS CPU RAM Disk Size Notes

Demo

10 K 5
  • Linux
  • Windows

2 Cores

3 GB

50 GB

Suitable for a laptop. 

Small

 50 K 50
  • Linux
  • Windows

8 Cores 

16 GB

400 GB

 

https://docs.appdynamics.com/display/PRO43/Controller+System+Requirements

 

 

 

Determine Controller host hardware size for non-production environment
3 REPLIES 3
AppDynamics Team

Re: Determine Controller host hardware size for non-production environment

Hi,

 

1) By two applications it means AppDynamics Business Applications. A logical grouping of nodes.

https://docs.appdynamics.com/display/PRO43/Business+Applications

 

2) There is no hard limit enforced that in demo profile you cannot monitor 5 nodes. Controller would allow you to monitor as many nodes as per your license irrespective of profile. But there would be metric drops, slow UI and controller crashes if the hardware/profile is not chosen correctly as the memory footprint required would be more depending on the number of agents reporting.

 

3) If 4.3, yes Contorller would allow you to install on a 4 Core machine. But starting 4.4 the Enterprise Console would validate hardware available based on profile chosen and would not let you install a controller profile if hardware reqs are not met.


Regards,

Saradhi

Re: Determine Controller host hardware size for non-production environment

Hi Saradhi,

 

Thanks for the info.

 

A related question: The "Licensed Unit" on the screenshot below, what does it refer to? Nodes or Apps?

 

Licence.PNG

AppDynamics Team

Re: Determine Controller host hardware size for non-production environment

https://docs.appdynamics.com/display/PRO43/License+Entitlements+and+Restrictions

 

1) For Java, one license unit allows you to instrument one JVM. 5 units allow you to instrument 5 JVMs.

 

2) For .NET one license unit entitles you to instrument an unlimited number of CLRs on a single Windows OS instance. Five units allow you to instrument unlimited CLRs on five Windows OS instances.

 

3) For java each JVM is one node. So 5 licenses is 5 nodes. But for .NET there can be many AppDynamics nodes based on the number of CLRs you instrument. So the number of nodes can be higher than the .NET license units.

 

4) Sizing is based on AppDynamics nodes. So if you instrument 50CLRs on one Windows instance that is one license and each can be a separate node. So you have 50 nodes and profile needs to be chosen accordingly.

 

Regards,
Saradhi