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

Output Queries-per-Second metric #997

Open
flaviomartins opened this issue Mar 21, 2024 · 4 comments
Open

Output Queries-per-Second metric #997

flaviomartins opened this issue Mar 21, 2024 · 4 comments

Comments

@flaviomartins
Copy link

What happens?

Every so often when working with a SQL Cell in Jupyterlab I wish to know the estimated QPS for that query formulation.

To Reproduce

It is difficult to do it using %%timeit since there is not easy way to %%capture the output and process it.

OS:

macOS

JupySQL Version:

0.10.9

Full Name:

Flavio Martins

Affiliation:

Instituto Superior Técnico

@flaviomartins
Copy link
Author

I am wondering if jupysql could even parse the output of EXPLAIN for this, but here is a reference for a kernel agnostic option that considers the whole cell execution-time deshaw/jupyterlab-execute-time#115

@edublancas
Copy link

I am wondering if jupysql could even parse the output of EXPLAIN for this, but here is a reference for a kernel agnostic option that considers the whole cell execution-time deshaw/jupyterlab-execute-time#115

seems like the execute-time extension already gives what you're looking for right? is anything missing?

@flaviomartins
Copy link
Author

execute-time displays the total elapsed time for the execution of the cell e.g., 20ms. I think displaying how many times this can be executed in a second makes sense: 1000/20 = 50 QPS

@edublancas
Copy link

Got it. I think it'd be relatively simple to add this. Unfortunately, the team is pretty time-constrained, but if you'd like to give it a try, that'd be great!

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

No branches or pull requests

2 participants