Skip to content

Controller Impact

Daniel Odievich edited this page May 3, 2019 · 4 revisions

DEXTER uses variety of REST APIs to extract data from the Controller. Some of the steps run sequentially, and others in parallel.

The number of parallel threads used in each of the extraction steps has been arrived to by experimentation and is designed to emulate moderate, but not excessive load from the users.

Metadata, Configuration, Event and Metric extractions have a fairly negligible impact on the Controller.

APM Snapshots are considerably more expensive to get out. The new improvements in 4.5 with Snapshot repository being moved out of MySQL data store to Events Store makes that effort much nicer on the controller.

Avoid running multiple AppDynamics DEXTER extracts against the same Controller because the load is multiplied.

Once extraction is done, the Controller is no longer touched by any processes.

Clone this wiki locally