Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
04-16-2019 02:26 AM
We embed the appdynamic nodejs agent in our nodejs service.
When disable appdynamics function, with 90 tps, our nodejs service CPU usage is 40%.
When enable appdynamics function, with 90 tps, our nodejs service CPU usage is 60%.
After follow the optimize steps from https://community.appdynamics.com/t5/Knowledge-Base/How-do-I-troubleshoot-high-CPU-usage/ta-p/23266, CPU usage still 60%, not any approvement!
04-16-2019 12:31 PM
Hi Jesseka,
For Node.js, it is usually process snapshots which lead to the CPU overhead. You can find the settings to tweak this in this document: https://docs.appdynamics.com/display/PRO45/Node.js+Settings+Reference
maxProcessSnapshotsPerPeriod
: Optional. The default is 2
. The number of automatic process snapshots allowed in processSnapshotCountResetPeriodSeconds seconds.
processSnapshotCountResetPeriodSeconds
: Optional, defaults to 60
. Frequency, in seconds, at which the automatic process snapshot count is reset to 0.
autoSnapshotDurationSeconds
: Optional, defaults to 10. Length, in seconds, of automatically-triggered process snapshots.Regards,
Kyle
Thanks,
Kyle Furlong, Technical Lead (C++ and Dynamic Languages)
04-16-2019 07:36 PM - edited 04-16-2019 07:38 PM
04-16-2019 07:36 PM
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!
04-17-2019 09:43 AM
Thanks,
Kyle Furlong, Technical Lead (C++ and Dynamic Languages)
04-18-2019 02:21 AM
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!
05-14-2019 10:41 AM
Is there any resolution for this?
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form