Insights Best Practices for Optimal Performance

Before you start you should know

• Insights is our reporting feature within the Assignar Web App.
• Use by those who are Reporting or Analyzing data in Assignar across your company.

Who this feature is for

• Users with an Insights Creator or Viewer license
• Insights Licensing Creator vs Viewer Seats

Best Practices for Optimal Performance:

To ensure the best possible experience for your team and all users of the Insights module, we'd like to highlight some important best practices:

1. Use Date Filters in your reporting: When creating or running reports, always use appropriate date filters to limit the amount of data being queried and processed. This significantly improves your report generation speed and overall system performance.
2. Avoid Large Data Sets: Be mindful of the data volume in your reports, especially for scheduled reports. Large data sets require more processing time and resources, which impacts performance.
3. Schedule Reports Wisely: When setting up scheduled reports, please carefully consider the frequency. We recommend avoiding very frequent schedules, such as multiple runs within an hour. This helps maintain optimal performance for all users.
4. Regular Review: Periodically review your scheduled reports to ensure they're still necessary and optimised. Consider archiving or deleting reports that are no longer needed

By following these guidelines, you can help us maintain the high performance of the Insights module for all customers while still getting the valuable data you need for your business.

• Apply Data Filtering
  • Insights applies a limit of 5000 rows on executed queries. When this row limit is reached, important rows might be missed, leading to incomplete results. Without limiting rows, queries can fetch too much data, slowing down performance and causing dashboards to load slowly.
    Its recommended to limit rows to ensure faster queries, more focused data, and makes dashboards load faster. To limit row fetching, use filters to narrow the data to relevant information. Apply date filters or other criteria to limit the data range.

• Limit the number of merged queries
  • It improves performance by reducing query complexity. It simplifies troubleshooting by making it easier to identify issue. While there is no specific limit to the number of merged queries a tile can have, but its recommended to avoid creating dashboard tile with more than 25 merged queries for better performance.

• Avoid overloading dashboard with too many tiles
  • Having too many tiles with complex queries can slow down dashboard loading. Each tile can trigger its own query, leading to multiple background queries and longer load time. While there is no specific limit to the number of tiles in a dashboard we can have but we generally recommend limiting to 4 tiles for better performance.

• Dashboard Auto-refresh feature
  • To optimise performance with auto-refresh, set a refresh interval that isn’t too frequent. We recommend no more frequent than 15 minutes. Avoid refreshing too often, especially for large datasets, to maintain faster loading times.

• Avoid fetching too many columns
  • Too many columns can increase query complexity / data fetched and therefore slow down query performance. We support up to 200 columns for query results but for better performance, 50 or fewer columns is recommended.