GSF Impact Framework extension for the Microsoft Azure Data Studio Tool - Calculate the Impacts of SQL Query payloads

[tellingmachine]

Prize category

Best Content

Overview

Microsoft Azure Data Studio (https://github.com/microsoft/azuredatastudio) is a database administration tool that is written as an Electron application. It supports a wide range of database systems and runs on Windows, Linux and IOS. It provides SQL Query performance metrics. The goal of the Hack is to build an Azure Data Studio Extension (https://github.com/microsoft/azuredatastudio/wiki/List-of-Extensions) and an SQL Query Impact Framework extension that can hack into these performance metrics and produce impact estimates. Azure Data Studio also supports (Jupyter) Notebooks. As part of the GSF Extension for Azure Data Studio I would like to deliver a Notebook that introduces the Green Software Foundation and basics of the Impact Framework, besides demonstrating how to use the extension with SQL Query payloads.

Questions to be answered

No response

Have you got a project team yet?

No, but we will find people ourself

Project team

No response

Terms of Participation

• [X] I agree to the hackathon Rules & Terms and Code of Conduct

[jawache]

Hi @tellingmachine

Very interesting!

What metrics (observations) can you gather from the studio? Any thoughts on what you need to turn those observations into impact?

With the current - set of plugins as long as you can get from your metrics to something like an equivalent CPU utilisation then the existing plugins can get you the rest of the way into carbon impacts.

I'm really keen to see some models that can induce the types of observations you can make from databases into impacts. For example, naively, most people would be able to observe GB saved/read, if there was a simple model that approximated energy/carbon from GB that would be something that would instantly be used in many places, it's been a very common ask.

Is this along the lines of what you're proposing:

• studio exports a manifest file with all the observations, configuration, plugins all ready to run.
• you might need to create some of your own plugins to fill any gaps in the pipeline to carbon.
• the end user can take that and do what they want, add it to a report, experiment with the coefficients and rerun to do some scenario analysis etc... it's a written audit of the emissions of their database.
• be able to load the manifest and run it via a jupyter notebook.

[tellingmachine]

I am confused. I don't see this idea in the main Carbon Hack roster. What do I need to do to get it there?

[russelltrow]

Hey @tellingmachine I've replied to your discussion. Your project is definitely on the CH roster, we just need you to complete the registration form

[tellingmachine]

Thanks for the clarification. I accidentally unassigned myself from this discussion. Would you please assign me again? Also, how do I assign team members to this discussion.