Performance Issues with Package Execution

Several customers have reported sudden performance issues when running packages frequently.

Background

• Execution Frequency: Packages are executed every five minutes.
• Execution Time: Each package takes approximately 1 minute to complete.
• Execution Method: Agent is used for scheduling and execution.

The Problem

If the source database server fails, package execution can get stuck, leading to cascading issues:

• Execution Overlap: Multiple instances of aetlcl.exe become stuck.
  • After 1 hour: 12 stuck instances.
  • After 24 hours: 288 stuck instances.
• System Impact: The server becomes unresponsive due to high memory usage.

Symptoms:

1. Increased number of stuck processes visible in Task Manager.

2. Execution log showing excessive resource usage.

Solution

1. Set Terminate on Timeout

This ensures stuck processes are automatically terminated if they exceed a specified duration.

2. Enable Execute One Action at a Time

This prevents multiple actions from running concurrently, avoiding process bottlenecks and resource contention.

By applying these settings, system stability and performance can be significantly improved.

Posted on March 14, 2023 • 1 min read • 194 words