You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, it's almost impossible to tell how long the query run on the database as Metabase does not show any indication anywhere regarding time. I've noticed today in the Dev Tools that actually api/dataset endpoint returns running_time property which from what I see is time in milliseconds. Could we maybe show this data when running raw SQL query in New -> SQL Query window?
Describe the solution you'd like
Show elapsed time in seconds/milliseconds in the bottom right corner near the number of returned rows, e.g.
Describe alternatives you've considered
Looking in Dev Console for every query
How important is this feature to you?
As a developer I am very focused on the performance of my queries so it would be great to get that information
Additional context
Screenshot posted above
The text was updated successfully, but these errors were encountered:
@paoliniluis the tab goes away so if you are not looking (e.g. brewing tea) you have no idea for how long it run. Also, on the tab it's shown after 10s so for shorter queries you don't have the data at all.
Is your feature request related to a problem? Please describe.
Currently, it's almost impossible to tell how long the query run on the database as Metabase does not show any indication anywhere regarding time. I've noticed today in the Dev Tools that actually
api/dataset
endpoint returnsrunning_time
property which from what I see is time in milliseconds. Could we maybe show this data when running raw SQL query inNew -> SQL Query
window?Describe the solution you'd like
Show elapsed time in seconds/milliseconds in the bottom right corner near the number of returned rows, e.g.
Describe alternatives you've considered
Looking in Dev Console for every query
How important is this feature to you?
As a developer I am very focused on the performance of my queries so it would be great to get that information
Additional context
Screenshot posted above
The text was updated successfully, but these errors were encountered: