Handling Slow Performance in Data Exchange (DX)

Overview

This article covers common causes and solutions for slow performance in Data Exchange (DX) when retrieving or exporting ReqIF files. It includes troubleshooting steps, potential issues with API performance, and recommendations for optimizing DX usage.

1. Identifying the Cause of Slow Performance

✔ System Resource Utilization:

• DX is a client-based tool and heavily depends on the local machine’s CPU and memory.

• High data volume exports can cause performance bottlenecks.

• Running DX on a Virtual Machine (VM) instead of a local machine may improve performance.

✔ Database Performance Issues:

• DX operations may be affected by database queries, especially if there is DB quorum loss or deadlocks in the database.

• SaaSOps teams may investigate database-related issues if performance degradation is reported.

✔ Old Relationship API Usage:

• Older versions of DX (before 3.8.4) relied on a legacy GET relationships API, which was significantly slower.

• Newer versions (3.8.4+) include optimized relationship retrieval, improving speed and reducing API overhead.

✔ License Version Restrictions:

• Check if the customer’s license is pinned to a specific DX version.

• If so, upgrading DX may not be straightforward and may require a new license.

2. Recommended Fixes and Optimizations

✅ Upgrade DX to Version 3.8.4 or Later

• Performance optimizations for relationship retrieval were introduced in DX 3.8.4.

• Users running DX 3.8.3 or older should upgrade to take advantage of the improved API performance.

✅ Monitor Database Performance

• If DB quorum loss is detected, coordinate with the SaaSOps team for investigation.

• If necessary, hold off on large exports until DB issues are resolved.

✅ Optimize Data Volume for Export

• Large data exports can slow down performance.

• Users should filter and segment data where possible before running large exports.

✅ Ensure API Compatibility

• If using an older Jama Connect version, confirm that relationship API updates are included.

• Ensure that DX and Jama versions align for optimal performance.

✅ Check Machine Resource Allocation

• Ensure the machine running DX has sufficient CPU and memory.

• Running DX in a high-performance VM may yield better results.

3. Best Practices for Avoiding Performance Issues

🚀 Upgrade to DX 3.8.4+ to benefit from API performance improvements.
🚀 Limit export size to avoid overwhelming system resources.
🚀 Monitor system CPU/memory usage if performance degradation occurs.
🚀 Coordinate with SaaSOps if DB quorum issues are suspected.
🚀 Ensure the user has an updated DX license before upgrading.

4. Conclusion

Slow DX performance can be caused by system resource limits, outdated APIs, database issues, or license restrictions. The best way to address performance issues is to upgrade to DX 3.8.4+, optimize data exports, and ensure API compatibility with the latest Jama Connect versions.