Discussion Feed

 Thanks!   We have tested the follow four scenarios with 90 tps ,  still get the same result. scenarios 1:  AppDynamics is disabled      ----  nodejs agent CPU used  41% scenarios 2: AppDynamics is enabled with default setting (processSnapshotCountResetPeriodSeconds: 60, maxProcessSnapshotsPerPeriod: 2,  autoSnapshotDurationSeconds: 10 )        ----  nodejs agent CPU used  57% scenarios 3: AppDynamics is enabled with special setting, (processSnapshotCountResetPeriodSeconds: 60, maxProcessSnapshotsPerPeriod: 10,  autoSnapshotDurationSeconds: 6 )         ----  nodejs agent CPU used  61% scenarios 4: AppDynamics is enabled with special setting (processSnapshotCountResetPeriodSeconds: 120, maxProcessSnapshotsPerPeriod: 1,  autoSnapshotDurationSeconds: 10 )      ---  nodejs agent CPU used  56%   regards! ... View more

Hi Kyle,               Thanks for the reply!                We have tried adjust the three paramters(autoSnapshotDurationSeconds, processSnapshotCountResetPeriodSeconds, maxProcessSnapshotsPerPeriod), even set the alwaysAddEumMetadataInHttpHeaders to false for test,   but still get the same result of high CPU usage .                Here is our Nodejs test code, const appdynamics= require("appdynamics"); appdynamics.profile({ controllerHostName: appdynamicsConf.controllerHostName, controllerPort: appdynamicsConf.controllerPort, controllerSslEnabled: appdynamicsConf.controllerSslEnabled, accountName: appdynamicsConf.accountName, accountAccessKey: appdynamicsConf.accountAccessKey, applicationName: appdynamicsConf.applicationName, autoSnapshotDurationSeconds: 60, processSnapshotCountResetPeriodSeconds: 120, maxProcessSnapshotsPerPeriod: 1, alwaysAddEumMetadataInHttpHeaders: false, tierName: appdynamicsConf.tierName, nodeName: os.hostname() });   Regards!   ... View more