Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show query running time on UI #29482

Open
simivar opened this issue Mar 23, 2023 · 3 comments · May be fixed by #29486
Open

Show query running time on UI #29482

simivar opened this issue Mar 23, 2023 · 3 comments · May be fixed by #29486

Comments

@simivar
Copy link

simivar commented Mar 23, 2023

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.
image

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

@paoliniluis
Copy link
Contributor

It's currently on the tab

@simivar
Copy link
Author

simivar commented Mar 24, 2023

@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.

@paoliniluis
Copy link
Contributor

similar to #9408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants