Load Testing with DotNet and Sharepoint Agent
Article ID: 74936
Updated On:
Products
APP PERF MANAGEMENT
CA Application Performance Management Agent (APM / Wily / Introscope)
CUSTOMER EXPERIENCE MANAGER
INTROSCOPE
Issue/Introduction
APM Support can only provide limited and general guidance on Agent load testing. Instead seek guidance in the APM Development Community Group.
We are seeing an issue with the performance of our IIS Sharepoint application when we run load test of 30K+ users when CA APM is instrumented. The symptoms include worker threads being maxed out as well at CPU topping out resulting in a failed test.
When we remove CA APM from the servers and perform the same load test the results are acceptable.
What is the level of overhead we should be expecting when CA APM is instrumented?
We are seeing an issue with the performance of our IIS Sharepoint application when we run load test of 30K+ users when CA APM is instrumented. The symptoms include worker threads being maxed out as well at CPU topping out resulting in a failed test.
When we remove CA APM from the servers and perform the same load test the results are acceptable.
What is the level of overhead we should be expecting when CA APM is instrumented?
Environment
This was tested with
- an APM 10.5.1 EM
- an APM 10.3 agent
But can apply to any release.
- an APM 10.5.1 EM
- an APM 10.3 agent
But can apply to any release.
Resolution
The customer successfully reached 40,000 login sessions by doing the following
1) Disabling the Sharepoint agent.
2) Following the steps in https://docops.ca.com/ca-apm/10-3/en/ca-apm-sizing-and-performance/agent-performance/
and https://docops.ca.com/ca-apm/10-3/en/ca-apm-sizing-and-performance/agent-performance/#AgentPerformance-GuidelinesforMeasuringAgentOverhead
3) Change config settings
a) Set introscope.agent.sockets.reportRateMetrics=false
https://docops.ca.com/ca-apm/9-6/en/implementing-agents/net-agent/configure-the-net-agent/configure-net-agent-connection-metrics
b) https://communities.ca.com/thread/101036215
It has talks about turning off the following
RemotingClientProxyTracing
DirectoryServicesTracing
MessagingTracing
MessagingTransactionTracing
SQLAgentDataReaders
SQLAgentTransactions
c) Enable/disable tracking in the monitored code for Application Map
introscope.agent.appmap.enabled=false. You may need this functionality
# Change to this property takes effect immediately and do not require the managed application to be restarted.
d) Other properties
introscope.agent.appmap.intermediateNodes.enabled=false
introscope.agent.bizRecording.enabled=false
introscope.agent.sqlagent.sql.turnoffmetrics=true
1) Disabling the Sharepoint agent.
2) Following the steps in https://docops.ca.com/ca-apm/10-3/en/ca-apm-sizing-and-performance/agent-performance/
and https://docops.ca.com/ca-apm/10-3/en/ca-apm-sizing-and-performance/agent-performance/#AgentPerformance-GuidelinesforMeasuringAgentOverhead
3) Change config settings
a) Set introscope.agent.sockets.reportRateMetrics=false
https://docops.ca.com/ca-apm/9-6/en/implementing-agents/net-agent/configure-the-net-agent/configure-net-agent-connection-metrics
b) https://communities.ca.com/thread/101036215
It has talks about turning off the following
RemotingClientProxyTracing
DirectoryServicesTracing
MessagingTracing
MessagingTransactionTracing
SQLAgentDataReaders
SQLAgentTransactions
c) Enable/disable tracking in the monitored code for Application Map
introscope.agent.appmap.enabled=false. You may need this functionality
# Change to this property takes effect immediately and do not require the managed application to be restarted.
d) Other properties
introscope.agent.appmap.intermediateNodes.enabled=false
introscope.agent.bizRecording.enabled=false
introscope.agent.sqlagent.sql.turnoffmetrics=true
Additional Information
What sort of load impact that the Sharepoint extension should have? It should be low impact around 5-15% of the baseline
Feedback
Powered by
