Metadata-Version: 2.1
Name: quisby
Version: 0.2
Summary: Quisby is a tool to provide first view into the results from various benchmarks such as linpack, streams, fio etc.
Home-page: https://github.com/sourabhtk37/Quisby
Author: T K Sourab
Author-email: tsourab@redhat.com
Requires-Python: >=3.9,<4.0
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Requires-Dist: boto3 (>=1.17.97,<2.0.0)
Requires-Dist: bs4 (>=0.0.1,<0.0.2)
Requires-Dist: google-api-core (>=1.30.0,<2.0.0)
Requires-Dist: google-api-python-client (>=2.9.0,<3.0.0)
Requires-Dist: google-auth-oauthlib (>=0.4.4,<0.5.0)
Requires-Dist: google_api (>=0.1.12,<0.2.0)
Description-Content-Type: text/markdown

## Quisby 

###### (Unoffical name) Quisby: An idler; one who does not or will not work. (noun)

Quisby is a tool to provide first view into the results from various benchmarks such as linpack, streams, fio etc. It doesn't aim to replace existing data viz tool but rather to provide a simplified view to the data with basic metric to understand the benchmark results from a higher level view. For detailed view, there are other tools such as pbench-dashboard, js-charts etc at hand.

Bechmarks currently supported:

|   Benchmark   |   Source data  |
|---|---|
| linpack | Benchmark result     |
| streams | Summary result       |
| uperf   | Summary csv result   |
| specjbb | Benchmark result     |
| pig     | Benchmark  result    |
| hammerDB| Benchmark  result    |
| fio     | pbench result        |
| autohpl | Summary  result      |
| aim     | Benchmark  result    |
| etcd    | pbench  result       |
| reboot  | Benchmark  result    |
| speccpu | Benchmark  result    |


### What it does

It extracts data from benchmark results file or summary results produced by wrapper benchmark programs and move that results to Google Sheet via sheets API V4. 

### Development 

```bash
#Clone the repo
git clone git@github.com:sourabhtk37/data-to-sheet.git

# Installation
source ./install.sh
(optional, for configuring aws and/or azure cli)
source ./install -aws -azure
```
#### config.py 

`config.py` is the only file you need to edit. Sample example have been provided in the file. 

####  quisby.py

This is the main driver program that will be called once you have edited `config.py` file accordingly. It takes in an input file with list of location to the test results.

The location file will look like:

``` 
test: results_linpack
</path/to/results>
...
test: pbench_fio
<http url with results>
...
```

```bash
quisby process --os-type <add-here> --os-release <add-here> --cloud-type <add-here>  location_file`
```
For more information on options, run:

    `quisby -h`

*That's it. It will return a google sheet. Visit the google sheet page and you will see a newly created spreadsheet with the data populated and graphed.*

### Comparison

If you want to compare two different OS release of similar system type then there are scripts that will help you to create a spreadsheet for the same. 

and then run:

```bash
quisby compare --test-name <benchmark-name-(optional)>  --spreadsheets <spreadsheet1,spreadsheet2>
```
and it would return a newly created spreadsheet with the comparison data.

## Contributing

Create issues and create a seperate feature branch to work on it. Push the changes to your clone repo and then create a pull request to the master branch of the origin repo.

