Agility Performance Improvements
The Agility engineering team’s efforts in the last two service packs has focused on improving core product performance, to ensure a positive user experience throughout the Agility product. Recent testing has shown significant improvements in the search functionality, and in the coming months, our team of engineers will continue to focus on improving the performance of searches in Agility by integrating with best-of-breed search and analytics engines. We have also improved the speed of login to the Agility Modular Interface (AMI) by deferring the resolution of special characters until they’re required.
In the next major release of Agility, 7.2, we have made exciting improvements to the performance of the AQL queries executed via the API. This will further improve the performance of both the Agility core functionality and all integrations, such as connectors to InDesign and other third-party systems.
Tips for Improving Agility Performance for Existing Users
- Ensure database statistics are up to date.
- Ensure database indexes are built regularly.
- Verify that application server is operating at optimal efficiency by assuring that there is available memory and space for processing.
- Determine that all other environmental elements are functioning correctly, such as database performance or network latency.
- Regularly empty Agility Structure BINs, to cut down the number of edges in the data.
- Contact us about running the Agility Health Check utility.
If you’re interested in running this utility then contact your Magnitude Customer Success Representative.
- Change your logging levels back down if you’ve raised them to generate diagnostics for an issue you’ve reported.
Contact Magnitude Support if you wish to discuss how to achieve this.
How Agility Support Can Help
We hope you already have access to the Magnitude Community, where incidents can be raised with us. If not, you can register for access at the following URL: https://magnitude.com/online-support/ and then select the Register here option.
To help us to help you in the most efficient way when raising an incident with us, we need as much information as possible. We ask for this up-front as it negates the need for constant back and forth, asking for further information.
We need detail of the issue that’s being reported, along with the steps undertaken to replicate the issue. Please include screen shots, videos or log files that better explain the situation. If you are reporting a performance issue, then be sure to include timings highlighting the performance degradation you see. It is also worth verifying with your own database and network teams that there is not a known cause of the issue from your side.
How to Generate and Find Logs in Agility
The information below covers details and screenshots of how to generate and find logs. There are three main log locations: the logs for AMI, for the application server and for InDesign Connector. Examples of these locations are shown below.
AMI’s System Information dialog has the Generate Diagnostic File button to prepare logs for you:
The location of application server logs depends on which app server you’re using and where it has been installed. Some examples of application server log locations, for Windows, are:
|Websphere||<drive>\Program Files (x86)\IBM\Websphere\AppServer\profiles\AppSrv01\logs\|
Similarly, the exact location of InDesign Connector logs depends on the version of InDesign you’re using and where it was installed. An example location, for MacOS, is:
You could also use the InDesign menu option of Agility > Utilities > Gather Diagnostics to prepare InDesign Connector log files.