Why does the execution time shown in Bold BI takes longer than actual database server?
Understanding Query Execution Time in Bold BI Logs
Query execution time in Bold BI logs is an important metric to understand when analyzing the performance of your data source connections, such as SQL, PostgreSQL, and Amazon Athena. This article will explain what is included in the query execution time in Bold BI logs and how it differs from the query execution time on actual database servers.
Components of Query Execution Time in Bold BI Logs
The query execution time in Bold BI logs includes the following components:
- Connection establishment time: This is the time taken to establish a connection with the databases.
- Query execution time: This is the actual time taken by the query to execute on the database
- Data transfer time: This is the time taken to move the data from the data source to the data table inside Bold BI after the query execution has completed.
The query execution time in Bold BI logs is the sum of these three components. It starts with the connection establishment and ends with the data being moved to the data table after the query execution has completed.
Difference between Query Execution Time in Bold BI Logs and Database servers
The query execution time on the server only includes the actual time taken by the query to execute on the data source. It does not include the connection establishment time or the data transfer time. Therefore, the query execution time in Bold BI logs is generally higher than the query execution time in the databases.
In summary, the query execution time in Bold BI logs provides a more comprehensive view of the time taken for a query to execute, including connection establishment and data transfer times. This information can be useful for optimizing your data source connections and improving the overall performance of your Bold BI dashboards.
You can get the query execution time for each widget in the Bold BI debug log file, as shown below.
The query execution time will be logged in the location - logs/bi.dataservice/debug-info.txt
Refer to this help document link to get the debug log files.
