How to troubleshoot slow Explorer queries

First, open the Network tab and run the query that's slow. You can see our tutorial on How to send a .har file to Support to see how to get to the Network tab.

The Network tab records (among other things) the traffic between Explorer and your Stardog server. It will show us both the queries we're running and how long they take.

Once you start recording traffic, you'll see information in six columns: Name, Status, Type, Initiator, Size, and Time. You can click on Time to sort by it and find the slowest queries.

Click on a query to open its information. You'll see six columns: Headers, Payload, Preview, Response, Initiator, and Timing. 

• Header: The endpoint the query was sent to and whether the request succeeded or failed (and a lot of other information).
• Payload: The query that was sent to your Stardog server.
• Preview: A preview of the Response.
• Response: The results of your query.
• Initiator: What initiated the query (Explorer in this case). Not important for our purposes.
• Timing: Where the time for this request was taken up.

If the timing tab shows the majority of the request's time being taken up in "Waiting for server response", your Stardog server is taking a long time to process the query. In this case, grab the query from the Payload tab, and profile the query in Studio. Send the query profile to Support.

Note the Payload tab will also include information on which graphs were queried in the "Query String Parameters" section, which is above "Form Data" (where the query itself is). Make sure you're querying the right graph on the right database so the query profiler profiles the correct query.