-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allow performance checking on SQL queries #56
Comments
This is a pretty interesting idea. Currently wondering if it's "enough" to deter console access, as I know that many are often ssh'ing in to:
However, I think some of that could be mitigated with some in-app guidance. |
Also, in the case that triggered this — I followed up with the dev, and the reason a normal perf check job wasn't run is still because
So we should probably wait on this to see if this resurfaces as a need once we are more stable and the majority of the jobs people run succeed instead of fail. (We never had people with this need on the old daemon) Related — we used to provide a link rack mini profiler results which contained more information about each query. Instead of providing granular access to the db, we could surface those results again if rack-mini-profiler is installed. |
I guess any time someone feels the needs to access the console is an indication of missing performance or debugging tools. |
Allow a developer to run SQL queries against the PerfCheck database so they can test performance and get EXPLAIN output without having to SSH into a PerfCheck server and get access to the database.
The text was updated successfully, but these errors were encountered: