How To Fix VIRT355 - CPU Bottleneck Indicator

SAP Error Message - Details

• Message type: E = Error

• Message class: VIRT - Virtualization Monitoring

• Message number: 355

• Message text: CPU Bottleneck Indicator

The CPU Bottleneck Indicator is only available for z/OS LPARs. It uses
the fact that RMF also reports Processor Delays and allows for a better
Analysis and Alerting. The semantic is agreed on by all SAP supported
virtualization platforms. The value range is 0-10. 0-5 is considered
o.k. ("green"), 6-7 mean "Warning"("Yellow") and 8-10 are "Red".
It is calculated according to the following table:
Delay,,,,log. CP Usage,,Bottleneck Indicator
0,,,,< 10 %,,,,0
0,,,,< 30 %,,,,1
0,,,,<50 %,,,,2
0,,,,<70 %,,,,3
0,,,,<90 %,,,,4
0,,,,90 % +,,,,5
1-2,,,,-,,,,,,6
3-4,,,,-,,,,,,7
5-6,,,,-,,,,,,8
7-8,,,,-,,,,,,9
10+,,,,-,,,,,,10,,,,,,,,,,

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VIRT355 - CPU Bottleneck Indicator ?

  The SAP error message VIRT355, which indicates a "CPU Bottleneck Indicator," typically arises when the system detects that the CPU resources are being overutilized, leading to performance degradation. This can occur in various scenarios, such as during peak processing times, inefficient coding, or inadequate hardware resources.
  Cause:
  
  High Workload: A sudden increase in transactions or background jobs can lead to CPU overload.
  Inefficient ABAP Code: Poorly optimized programs or queries can consume excessive CPU resources.
  Configuration Issues: Incorrect system configuration or parameters can lead to inefficient resource utilization.
  Insufficient Hardware: The existing CPU resources may not be adequate for the workload demands.
  Background Jobs: A large number of concurrent background jobs can lead to CPU contention.
  
  Solution:
  
  Analyze Workload: Use transaction codes like ST03N (Workload Analysis) or ST04 (Database Performance Analysis) to identify which processes are consuming the most CPU.
  Optimize ABAP Code: Review and optimize any custom ABAP programs or reports that are consuming excessive CPU time. Use tools like the ABAP Runtime Analysis (transaction SE30) to identify bottlenecks.
  Adjust System Configuration: Review and adjust system parameters related to CPU utilization, such as the number of work processes and their configuration.
  Hardware Upgrade: If the workload consistently exceeds the CPU capacity, consider upgrading the hardware or scaling out to additional application servers.
  Schedule Background Jobs: Stagger the execution of background jobs to avoid CPU spikes during peak hours.
  Monitor Performance: Continuously monitor system performance using tools like SAP Solution Manager or other monitoring solutions to proactively identify and address CPU bottlenecks.
  
  Related Information:
  
  SAP Notes: Check for relevant SAP Notes that may provide specific guidance or patches related to performance issues.
  SAP Community: Engage with the SAP Community forums for insights and shared experiences from other users facing similar issues.
  Performance Tuning Guides: Refer to SAP's performance tuning guides for best practices on optimizing system performance.
  
  By addressing the underlying causes and implementing the suggested solutions, you can mitigate the CPU bottleneck and improve overall system performance.