Using the Explore query tracker to monitor query performance

When a Looker Explore runs a database query, the query is executed in three phases, as follows:

The Explore query tracker displays the progress of an Explore query through these three phases.

If a query is taking a long time to execute, the query tracker can indicate which phase of the query is causing the performance issue. This is useful for identifying where performance problems may occur, and where optimization efforts can be the most effective.

To enable the query tracker, your Looker admin must enable the Explore Query Tracker Labs feature. Once enabled, the query tracker is displayed when an Explore is running as long as either the Explore Visualization panel or Data panel is open.

Query Initialization phase

During the Query Initialization phase, Looker is performing all of the tasks that are required before the query is sent to your database. The Query Initialization phase includes the following tasks:

Running Query phase

The Running Query phase is when Looker contacts and queries your database and returns the results of the query. Performance issues during this phase could indicate issue with the external database, such as PDTs that take a long time to rebuild and may need to be optimized, or external database tables that may need optimization. The Running Query phase includes the following tasks:

  • Building any PDTs in the database that are required for the Explore query
  • Running the requested query on the database

Processing Results phase

During the Processing Results phase, Looker processes and renders the results of the query. The Processing Results phase includes the following tasks:

Using the query tracker to troubleshoot query performance issues

Once you have identified which phase of a query is encountering possible performance issues, you can use the following resources to help further identify query performance trends and anomalies: