On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
14 rates
This topic contains information to help you estimate the hardware requirements for a remote Analytics Agent deployment where a single Analytics Agent is aggregating transaction events from multiple APM Application Agents. This guide covers transaction analytics only. 

There are two basic issues regarding sending analytics data to a remote Analytics Agent: 

  • How many APM agents can report to one remote Analytics Agent?
  • What are the machine requirements for hosting the remote Analytics Agent?

Don't extract the numbers in this guide to sizing for Log Analytics because the Analytics Agent must be installed on the local machine to capture Log Analytics. 

Analytics Agent Sizing Based on Event Volume

Based on our testing, the volume of events being sent to the Analytics Agent is the limiting factor in determining how many APM agents can report to one remote Analytics Agent.

 The tests were conducted on virtual hardware and programmatically generated work load. Real world work loads may vary. To best estimate your hardware sizing requirements, carefully consider the traffic patterns in your application and test in a test environment that closely resembles your production application and user activity.

Calculating Analytics Event Volume

One business transaction can traverse many tiers. In each tier, one business transaction traverses one node. One node produces one request per business transaction when the transaction is synchronous. For async transactions, multiple events may be generated by a node for a single request. One request equals one analytics event. To calculate how many events a business transaction generates, you need to count the number of tiers/nodes that are sending data into the Analytics Agent.

You can estimate the number of events using the following formula:

One business transaction generates events at a rate = calls per minute times the number of tiers reporting analytics data for the business transaction.

In simple terms: #events for one business transaction = calls per minute times # of tiers.

Characteristics of the Amazon EC2 Instance Types

For complete information on Amazon EC2 instance types, see https://aws.amazon.com/ec2/instance-types/.

The testing was performed using c3.large, c3.xlarge, and c4.4xlarge.

 

ModelvCPUMem (GiB)SSD Storage  (GB)
c3.large23.752 x 16
c3.xlarge47.52 x 40
c4.4xlarge1630EBS-Only

Testing Results 

Raw Data

Analytics Agent Host MachineAnalytics Agent events/minTotal CPU%JVM Heap (Mb)
c3.large5231317%468
c3.large5483117%470
c3.large7074624%475
c3.large7454124%477
c3.large7734423%487
c3.large9707428%512
c3.large11599936%519
c3.large13914343%526
c3.large14878247%587
c3.large20407365%527
c3.large24754380%624
c3.large24926181%637
    
c3.xlarge19628833%518
c3.xlarge25458644%727
c3.xlarge30268951%497
c3.xlarge33687958%913
c3.xlarge37251565%1024
c3.xlarge51359891%922
c3.xlarge47895478%922
c3.xlarge42000069%979
c3.xlarge37603461%1024
c3.xlarge31800052%1024
c3.xlarge25800043%1024
c3.xlarge19800032%1024
c3.xlarge14400022%1024
    
c4.4xlarge53490017%552
c4.4xlarge60472519%841
c4.4xlarge71614123%1024
  • No labels