| Name | hedra JSON |
| Version |
0.7.24
JSON |
| download |
| home_page | None |
| Summary | Performance testing at scale. |
| upload_time | 2024-10-30 00:20:24 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.10 |
| license | MIT License Copyright (c) 2022 scorbettUM Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
pypi
cicd
python
performance
testing
dag
graph
workflow
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# <b>Hedra - Testing at scale </b>
[](https://pypi.org/project/hedra/)
[](https://github.com/scorbettUM/hedra/blob/main/LICENSE)
[](https://github.com/scorbettUM/hedra/blob/main/CODE_OF_CONDUCT.md)
[](https://pypi.org/project/hedra/)
| Package | Hedra |
| ----------- | ----------- |
| Version | 0.7.24 |
| Web | https://hedra.dev |
| Download | https://pypi.org/project/hedra/ |
| Source | https://github.com/scorbettUM/hedra |
| Keywords | performance, testing, async, distributed, graph, DAG, workflow |
Hedra is a Python performance and scalable unit/integration testing framework that makes creating and running complex test workflows easy.
These workflows are written as directed acyclic graphs in Python, where each graph is specified as a collection of Python classes referred to as <b>stages</b>. Each Stage may then specify async Python methods which are then wrapped in Python decorators (referred to as <b>hooks</b>), which that Stage will then execute. The hook wrapping a method tells Hedra both what the action does and when to execute it. In combination, stages and hooks allow you to craft test workflows that can mimic real-world user behavior, optimize framework performance, or interact with a variety of Hedra's powerful integrations.
<br/>
___________
## <b> Why Hedra? </b>
Understanding how your application performs under load can provide valuable insights - allowing you to spot issues with latency, memory usage, and stability. However, performance test tools providing these insights are often difficult to use and lack the ability to simulate complex user interaction at scale. Hedra was built to solve these problems by allowing developers and test engineers to author performance tests as sophisticated and scalable workflows. Hedra adheres to the following tenants:
<br/>
### __Speed and efficiency by default__
Regardless of whether running on your personal laptop or distributed across a cluster, Hedra is *fast*, capable of generating millions of requests or interactions per minute and without consuming excessive memory. Hedra pushes the limits of Python to achieve this, embracing the latest in Python async and multiprocessing language features to achieve optimal execution performance.
<br/>
### __Run with ease anywhere__
Authoring, managing, and running test workflows is easy. Hedra includes integrations with Git to facilitate easy management of collections of graphs via <b>Projects</b>, the ability to generate flexible starter test templates, and an API that is both fast and intuitive to understand. Distributed use almost exactly mirrors local operation, reducing the learning curve for more complex deployments.
<br/>
### __Flexibility and and painless extensibility__
Hedra ships with support for HTTP, HTTP2, Websockets, and UDP out of the box. GraphQL, GRPC, and Playwright are available simply by installing the (optional) dependency packages. Hedra offers JSON and CSV results output by default, with 28 additional results reporting options readily available by likewise installing the required dependencies.
Likewise, Hedra offers a comprehensive plugin system. You can easily write a plugin to test your Postgresql database or integrate a third party service, with CLI-generated templates to guide you and full type hints support throughout. Unlike other frameworks, no additional compilation or build steps are required - just write your plugin, import it, and include it in the appropriate Stage in your test graph.
<br/>
___________
## <b>Requirements and Getting Started</b>
Hedra has been tested on Python versions 3.8.6+, though we recommend using Python 3.10+. You should likewise have the latest LTS version of OpenSSL, build-essential, and other common Unix dependencies installed (if running on a Unix-based OS).
*<b>Warning</b>*: Hedra has currently only been tested on the latest LTS versions of Ubuntu and Debian. Other official OS support is coming Mar. 2023.
<br/>
### __Installing__
To install Hedra run:
```
pip install hedra
```
Verify the installation was was successful by running the command:
```
hedra --help
```
which should output
<br/>
### __Creating your first graph__
Get started by running Hedra's:
```
hedra graph create <path/to/graph_name.py>
```
command in an empty directory to generate a basic test from a template. For example, run:
```
hedra graph create example.py
```
which will output the following:
and generate the the test below in the specified `example.py` file:
```python
from hedra import (
Setup,
Execute,
action,
Analyze,
JSONConfig,
Submit,
depends,
)
class SetupStage(Setup):
batch_size=1000
total_time='1m'
@depends(SetupStage)
class ExecuteHTTPStage(Execute):
@action()
async def http_get(self):
return await self.client.http.get('https://<url_here>')
@depends(ExecuteHTTPStage)
class AnalyzeStage(Analyze):
pass
@depends(AnalyzeStage)
class SubmitJSONResultsStage(Submit):
config=JSONConfig(
events_filepath='./events.json',
metrics_filepath='./metrics.json'
)
```
We'll explain this graph below, but for now - replace the string `'https://<url_here>'` with `'https://httpbin.org/get'`.
<br/>
Before running our test, if on a Unix system, we may need to set the maximum number of open files above its current limit. This can be done
by running:
```
ulimit -n 256000
```
note that you can provide any number here, as long as it is greater than the `batch_size` specified in the `SetupStage` Stage. With that, we're ready run our first test by executing:
```
hedra graph run example.py
```
Hedra will load the test graph file, parse/validate/setup the stages specified, then begin executing your test:
The test will take a minute or two to run, but once complete you should see:
You have officially created and run your first test graph!
<br/>
___________
## <b>Development</b>
Local development requires at-minimum Python 3.8.6, though 3.10.0+ is recommended. To setup your environment run:
```
python3 -m venv ~/.hedra && \
source ~/.hedra/bin/activate && \
git clone https://github.com/scorbettUM/hedra.git && \
cd hedra && \
pip install --no-cache -r requirements.in && \
python setup.py develop
```
To develop or work with any of the additional provided engines, references the dependency tables below.
<br/>
___________
## <b>Engines, Personas, Algorithms, and Reporters</b>
Much of Hedra's extensibility comes in the form of both extensive integrations/options and plugin capabilities for four main framework features:
<br/>
### __Engines__
Engines are the underlying protocol or library integrations required for Hedra to performance test your application (for example HTTP, UDP, Playwright). Hedra currently supports the following Engines, with additional install requirements shown if necessary:
| Engine | Additional Install Option | Dependencies |
| ----------- | ----------- |------------ |
| HTTP | N/A | N/A |
| HTTP2 | N/A | h2, hpack |
| HTTP3 (unstable) | pip install hedra[http3] | aioquic |
| UDP | N/A | N/A |
| Websocket | N/A | N/A |
| GRPC | pip install hedra[grpc] | grpcio grpco-tools, h2, hpack |
| GraphQL | pip install hedra[graphql] | gql |
| GraphQL-HTTP2 | pip install hedra[graphql] | gql, h2, hpack |
| Playwright | pip install hedra[playwright] && playwright install | playwright |
<br/>
### __Personas__
Personas are responsible for scheduling when `@action()` or `@task()` hooks execute over the specified Execute stage's test duration. No additional install dependencies are required for Personas, and the following personas are currently supported out-of-box:
| Persona | Setup Config Name | Description |
| ---------- | ---------------- | ----------------- |
| Approximate Distribution (unstable) | approximate-distribution | Hedra automatically adjusts the batch size after each batch spawns according to the concurrency at the current distribution step. This Persona is only available to and is selected by default if a Variant of an Experiment is assigned a distribution. |
| Batched | batched | Executes each action or task hook in batches of the specified size, with an optional wait between each batch spawning |
| Constant Arrival Rate | constant-arrival | Hedra automatically adjusts the batch size after each batch spawns based upon the number of hooks that have completed, attempting to achieve `batch_size` completions per batch |
| Constant Spawn Rate | constant-spawn | Like `Batched`, but cycles through actions before waiting `batch_interval` time. |
| Default | N/A | Cycles through all action/task hooks in the Execute stage, resulting in a (mostly) even distribution of execution |
| No-Wait | no-wait | Cycles through all action/task hooks in the Execute stage with no memory usage or other waits. __WARNING__: This persona may cause OOM. |
| Ramped | ramped | Starts at a batch size of `batch_gradient` * `batch_size`. Batch size increases by the gradient each batch with an optional wait between each batch spawning |
| Ramped Interval | ramped-interval | Executes `batch_size` hooks before waiting `batch_gradient` * `batch_interval` time. Interval increases by the gradient each batch |
| Sorted | sorted | Executes each action/task hook in batches of the specified size and in the order provided to each hook's (optional) `order` parameter |
| Weighted | weighted | Executes action/task hooks in batches of the specified size, with each batch being generated from a sampled distribution based upon that action's weight |
<br/>
### __Algorithms__
Algorithms are used by Hedra `Optimize` stages to calculate maximal test config options like `batch_size`, `batch_gradient`, and/or `batch_interval`. All out-of-box supported algorithms use `scikit-learn` and include:
| Algorithm | Setup Config Name | Description |
| ---------- | ---------------- | ----------------- |
| SHG | shg | Uses `scikit-learn`'s Simple Global Homology (SHGO) global optimization algorithm |
| Dual Annealing | dual-annealing | Uses `scikit-learn`'s Dual Annealing global optimization algorithm |
| Differential Evolution | diff-evolution | Uses `scikit-learn`'s Differential Evolution global optimization algorithm |
| Point Optimizer (unstable) | point-optimizer | Uses a custom least-squares algorithm. Can only be used by assigning a distribution to a Variant stage for an Experiment. |
<br/>
### __Reporters__
Reporters are the integrations Hedra uses for submitting aggregated and unaggregated results (for example, to a MySQL database via the MySQL reporter). Hedra currently supports the following Reporters, with additional install requirements shown if necessary:
| Engine | Additional Install Option | Dependencies |
| ----------- | ----------- |------------ |
| AWS Lambda | pip install hedra[aws] | boto3 |
| AWS Timestream | pip install hedra[aws] | boto3 |
| Big Query | pip install hedra[google] | google-cloud-bigquery |
| Big Table | pip install hedra[google] | google-cloud-bigtable |
| Cassandra | pip install hedra[cassandra] | cassandra-driver |
| Cloudwatch | pip install hedra[aws] | boto3 |
| CosmosDB | pip install hedra[azure] | azure-cosmos |
| CSV | N/A | N/A |
| Datadog | pip install hedra[datadog] | datadog |
| DogStatsD | pip install hedra[statsd] | aio_statsd |
| Google Cloud Storage | pip install hedra[google] | google-cloud-storage |
| Graphite | pip install hedra[statsd] | aio_statsd |
| Honeycomb | pip install hedra[honeycomb] | libhoney |
| InfluxDB | pip install hedra[influxdb] | influxdb_client |
| JSON | N/A | N/A |
| Kafka | pip install hedra[kafka] | aiokafka |
| MongoDB | pip install hedra[mongodb] | motor |
| MySQL | pip install hedra[sql] | aiomysql, sqlalchemy |
| NetData | pip install hedra[statsd] | aio_statsd |
| New Relic | pip install hedra[newrelic] | newrelic |
| Postgresql | pip install hedra[sql] | aiopg, psycopg2-binary, sqlalchemy |
| Prometheus | pip install hedra[prometheus] | prometheus-client, prometheus-client-api |
| Redis | pip install hedra[redis] | redis, aioredis |
| S3 | pip install hedra[aws] | boto3 |
| Snowflake | pip install hedra[snowflake] | snowflake-connector-python, sqlalchemy |
| SQLite3 | pip install hedra[sql] | sqlalchemy |
| StatsD | pip install hedra[statsd] | aio_statsd |
| Telegraf | pip install hedra[statsd] | aio_statsd |
| TelegrafStatsD | pip install hedra[statsd] | aio_statsd |
| TimescaleDB | pip install hedra[sql] | aiopg, psycopg2-binary, sqlalchemy |
| XML | pip install hedra[xml] | dicttoxml |
<br/>
___________
## <b>Resources</b>
Hedra's official and full documentation is currently being written and will be linked here soon!
___________
## <b>License</b>
This software is licensed under the MIT License. See the LICENSE file in the top distribution directory for the full license text.
___________
## <b>Contributing</b>
Hedra will be open to general contributions starting Fall, 2023 (once the distributed rewrite and general testing is complete). Until then, feel
free to use Hedra on your local machine and report any bugs or issues you find!
___________
## <b>Code of Conduct</b>
Hedra has adopted and follows the [Contributor Covenant code of conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md).
If you observe behavior that violates those rules please report to:
| Name | Email | Twitter |
|------- |-------- |---------- |
| Sean Corbett | sean.corbett@umontana.edu | [@sc_codeum](https://twitter.com/sc_codeUM/) |
Raw data
{
"_id": null,
"home_page": null,
"name": "hedra",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": "pypi, cicd, python, performance, testing, dag, graph, workflow",
"author": null,
"author_email": "Ada Lundhe <sean.corbett@umconnect.edu>",
"download_url": "https://files.pythonhosted.org/packages/db/f4/c821caff9cc8cb449e6b722e335aa8f0e68e9ff6a8f58b8fa98105feee29/hedra-0.7.24.tar.gz",
"platform": null,
"description": "\n# <b>Hedra - Testing at scale </b>\n[](https://pypi.org/project/hedra/)\n[](https://github.com/scorbettUM/hedra/blob/main/LICENSE)\n[](https://github.com/scorbettUM/hedra/blob/main/CODE_OF_CONDUCT.md)\n[](https://pypi.org/project/hedra/)\n\n\n| Package | Hedra |\n| ----------- | ----------- |\n| Version | 0.7.24 |\n| Web | https://hedra.dev |\n| Download | https://pypi.org/project/hedra/ | \n| Source | https://github.com/scorbettUM/hedra |\n| Keywords | performance, testing, async, distributed, graph, DAG, workflow |\n\nHedra is a Python performance and scalable unit/integration testing framework that makes creating and running complex test workflows easy.\n\nThese workflows are written as directed acyclic graphs in Python, where each graph is specified as a collection of Python classes referred to as <b>stages</b>. Each Stage may then specify async Python methods which are then wrapped in Python decorators (referred to as <b>hooks</b>), which that Stage will then execute. The hook wrapping a method tells Hedra both what the action does and when to execute it. In combination, stages and hooks allow you to craft test workflows that can mimic real-world user behavior, optimize framework performance, or interact with a variety of Hedra's powerful integrations.\n\n<br/>\n\n___________\n\n## <b> Why Hedra? </b>\n\nUnderstanding how your application performs under load can provide valuable insights - allowing you to spot issues with latency, memory usage, and stability. However, performance test tools providing these insights are often difficult to use and lack the ability to simulate complex user interaction at scale. Hedra was built to solve these problems by allowing developers and test engineers to author performance tests as sophisticated and scalable workflows. Hedra adheres to the following tenants:\n\n<br/>\n\n### __Speed and efficiency by default__ \n\nRegardless of whether running on your personal laptop or distributed across a cluster, Hedra is *fast*, capable of generating millions of requests or interactions per minute and without consuming excessive memory. Hedra pushes the limits of Python to achieve this, embracing the latest in Python async and multiprocessing language features to achieve optimal execution performance.\n\n<br/>\n\n### __Run with ease anywhere__\n\nAuthoring, managing, and running test workflows is easy. Hedra includes integrations with Git to facilitate easy management of collections of graphs via <b>Projects</b>, the ability to generate flexible starter test templates, and an API that is both fast and intuitive to understand. Distributed use almost exactly mirrors local operation, reducing the learning curve for more complex deployments.\n\n<br/>\n\n### __Flexibility and and painless extensibility__\nHedra ships with support for HTTP, HTTP2, Websockets, and UDP out of the box. GraphQL, GRPC, and Playwright are available simply by installing the (optional) dependency packages. Hedra offers JSON and CSV results output by default, with 28 additional results reporting options readily available by likewise installing the required dependencies.\n\nLikewise, Hedra offers a comprehensive plugin system. You can easily write a plugin to test your Postgresql database or integrate a third party service, with CLI-generated templates to guide you and full type hints support throughout. Unlike other frameworks, no additional compilation or build steps are required - just write your plugin, import it, and include it in the appropriate Stage in your test graph.\n\n<br/>\n\n___________\n\n## <b>Requirements and Getting Started</b>\n\nHedra has been tested on Python versions 3.8.6+, though we recommend using Python 3.10+. You should likewise have the latest LTS version of OpenSSL, build-essential, and other common Unix dependencies installed (if running on a Unix-based OS).\n\n*<b>Warning</b>*: Hedra has currently only been tested on the latest LTS versions of Ubuntu and Debian. Other official OS support is coming Mar. 2023. \n\n<br/>\n\n### __Installing__ \n\nTo install Hedra run:\n```\npip install hedra\n```\nVerify the installation was was successful by running the command:\n```\nhedra --help\n```\n\nwhich should output\n\n![Output of the hedra --help command](https://github.com/scorbettUM/hedra/blob/main/images/hedra_help_output.png?raw=true \"Verifyin Install\")\n\n<br/>\n\n### __Creating your first graph__ \n\nGet started by running Hedra's:\n```\nhedra graph create <path/to/graph_name.py>\n```\ncommand in an empty directory to generate a basic test from a template. For example, run:\n```\nhedra graph create example.py\n```\nwhich will output the following:\n\n![Output of the hedra graph create example.py command](https://github.com/scorbettUM/hedra/blob/main/images/hedra_graph_create.png?raw=true \"Creating a Graph\")\n\nand generate the the test below in the specified `example.py` file:\n```python\nfrom hedra import (\n\tSetup,\n\tExecute,\n\taction,\n\tAnalyze,\n\tJSONConfig,\n\tSubmit,\n\tdepends,\n)\n\nclass SetupStage(Setup):\n batch_size=1000\n total_time='1m'\n\n\n@depends(SetupStage)\nclass ExecuteHTTPStage(Execute):\n\n @action()\n async def http_get(self):\n return await self.client.http.get('https://<url_here>')\n\n\n@depends(ExecuteHTTPStage)\nclass AnalyzeStage(Analyze):\n pass\n\n\n@depends(AnalyzeStage)\nclass SubmitJSONResultsStage(Submit):\n config=JSONConfig(\n events_filepath='./events.json',\n metrics_filepath='./metrics.json'\n )\n\n```\n\nWe'll explain this graph below, but for now - replace the string `'https://<url_here>'` with `'https://httpbin.org/get'`.\n\n<br/>\nBefore running our test, if on a Unix system, we may need to set the maximum number of open files above its current limit. This can be done\nby running:\n\n```\nulimit -n 256000\n```\n\nnote that you can provide any number here, as long as it is greater than the `batch_size` specified in the `SetupStage` Stage. With that, we're ready run our first test by executing:\n```\nhedra graph run example.py\n```\n\nHedra will load the test graph file, parse/validate/setup the stages specified, then begin executing your test:\n\n![Output of the hedra graph run example.py command](https://github.com/scorbettUM/hedra/blob/main/images/hedra_graph_run_example.png?raw=true \"Running a Graph\")\n\nThe test will take a minute or two to run, but once complete you should see:\n\n![Output of hedra from a completed graph run](https://github.com/scorbettUM/hedra/blob/main/images/hedra_graph_complete.png?raw=true \"A Complete Graph Run\")\n\nYou have officially created and run your first test graph!\n\n<br/>\n\n\n___________\n\n## <b>Development</b>\n\nLocal development requires at-minimum Python 3.8.6, though 3.10.0+ is recommended. To setup your environment run:\n\n```\npython3 -m venv ~/.hedra && \\\nsource ~/.hedra/bin/activate && \\\ngit clone https://github.com/scorbettUM/hedra.git && \\\ncd hedra && \\\npip install --no-cache -r requirements.in && \\\npython setup.py develop\n```\n\nTo develop or work with any of the additional provided engines, references the dependency tables below.\n\n<br/>\n\n___________\n\n## <b>Engines, Personas, Algorithms, and Reporters</b>\n\nMuch of Hedra's extensibility comes in the form of both extensive integrations/options and plugin capabilities for four main framework features:\n<br/>\n\n### __Engines__ \nEngines are the underlying protocol or library integrations required for Hedra to performance test your application (for example HTTP, UDP, Playwright). Hedra currently supports the following Engines, with additional install requirements shown if necessary:\n\n| Engine | Additional Install Option | Dependencies |\n| ----------- | ----------- |------------ |\n| HTTP | N/A | N/A |\n| HTTP2 | N/A | h2, hpack |\n| HTTP3 (unstable) | pip install hedra[http3] | aioquic |\n| UDP | N/A | N/A |\n| Websocket | N/A | N/A |\n| GRPC | pip install hedra[grpc] | grpcio grpco-tools, h2, hpack |\n| GraphQL | pip install hedra[graphql] | gql |\n| GraphQL-HTTP2 | pip install hedra[graphql] | gql, h2, hpack |\n| Playwright | pip install hedra[playwright] && playwright install | playwright |\n\n\n<br/>\n\n### __Personas__\n\nPersonas are responsible for scheduling when `@action()` or `@task()` hooks execute over the specified Execute stage's test duration. No additional install dependencies are required for Personas, and the following personas are currently supported out-of-box:\n\n| Persona | Setup Config Name | Description |\n| ---------- | ---------------- | ----------------- |\n| Approximate Distribution (unstable) | approximate-distribution | Hedra automatically adjusts the batch size after each batch spawns according to the concurrency at the current distribution step. This Persona is only available to and is selected by default if a Variant of an Experiment is assigned a distribution. |\n| Batched | batched | Executes each action or task hook in batches of the specified size, with an optional wait between each batch spawning |\n| Constant Arrival Rate | constant-arrival | Hedra automatically adjusts the batch size after each batch spawns based upon the number of hooks that have completed, attempting to achieve `batch_size` completions per batch |\n| Constant Spawn Rate | constant-spawn | Like `Batched`, but cycles through actions before waiting `batch_interval` time. |\n| Default | N/A | Cycles through all action/task hooks in the Execute stage, resulting in a (mostly) even distribution of execution |\n| No-Wait | no-wait | Cycles through all action/task hooks in the Execute stage with no memory usage or other waits. __WARNING__: This persona may cause OOM. | \n| Ramped | ramped | Starts at a batch size of `batch_gradient` * `batch_size`. Batch size increases by the gradient each batch with an optional wait between each batch spawning |\n| Ramped Interval | ramped-interval | Executes `batch_size` hooks before waiting `batch_gradient` * `batch_interval` time. Interval increases by the gradient each batch |\n| Sorted | sorted | Executes each action/task hook in batches of the specified size and in the order provided to each hook's (optional) `order` parameter |\n| Weighted | weighted | Executes action/task hooks in batches of the specified size, with each batch being generated from a sampled distribution based upon that action's weight |\n\n<br/>\n\n### __Algorithms__\n\nAlgorithms are used by Hedra `Optimize` stages to calculate maximal test config options like `batch_size`, `batch_gradient`, and/or `batch_interval`. All out-of-box supported algorithms use `scikit-learn` and include:\n\n| Algorithm | Setup Config Name | Description |\n| ---------- | ---------------- | ----------------- |\n| SHG | shg | Uses `scikit-learn`'s Simple Global Homology (SHGO) global optimization algorithm |\n| Dual Annealing | dual-annealing | Uses `scikit-learn`'s Dual Annealing global optimization algorithm |\n| Differential Evolution | diff-evolution | Uses `scikit-learn`'s Differential Evolution global optimization algorithm |\n| Point Optimizer (unstable) | point-optimizer | Uses a custom least-squares algorithm. Can only be used by assigning a distribution to a Variant stage for an Experiment. |\n\n<br/>\n\n### __Reporters__\n\nReporters are the integrations Hedra uses for submitting aggregated and unaggregated results (for example, to a MySQL database via the MySQL reporter). Hedra currently supports the following Reporters, with additional install requirements shown if necessary:\n\n| Engine | Additional Install Option | Dependencies |\n| ----------- | ----------- |------------ |\n| AWS Lambda | pip install hedra[aws] | boto3 |\n| AWS Timestream | pip install hedra[aws] | boto3 |\n| Big Query | pip install hedra[google] | google-cloud-bigquery |\n| Big Table | pip install hedra[google] | google-cloud-bigtable |\n| Cassandra | pip install hedra[cassandra] | cassandra-driver |\n| Cloudwatch | pip install hedra[aws] | boto3 |\n| CosmosDB | pip install hedra[azure] | azure-cosmos |\n| CSV | N/A | N/A |\n| Datadog | pip install hedra[datadog] | datadog |\n| DogStatsD | pip install hedra[statsd] | aio_statsd |\n| Google Cloud Storage | pip install hedra[google] | google-cloud-storage |\n| Graphite | pip install hedra[statsd] | aio_statsd |\n| Honeycomb | pip install hedra[honeycomb] | libhoney |\n| InfluxDB | pip install hedra[influxdb] | influxdb_client |\n| JSON | N/A | N/A |\n| Kafka | pip install hedra[kafka] | aiokafka |\n| MongoDB | pip install hedra[mongodb] | motor |\n| MySQL | pip install hedra[sql] | aiomysql, sqlalchemy |\n| NetData | pip install hedra[statsd] | aio_statsd |\n| New Relic | pip install hedra[newrelic] | newrelic |\n| Postgresql | pip install hedra[sql] | aiopg, psycopg2-binary, sqlalchemy |\n| Prometheus | pip install hedra[prometheus] | prometheus-client, prometheus-client-api |\n| Redis | pip install hedra[redis] | redis, aioredis |\n| S3 | pip install hedra[aws] | boto3 |\n| Snowflake | pip install hedra[snowflake] | snowflake-connector-python, sqlalchemy |\n| SQLite3 | pip install hedra[sql] | sqlalchemy |\n| StatsD | pip install hedra[statsd] | aio_statsd |\n| Telegraf | pip install hedra[statsd] | aio_statsd |\n| TelegrafStatsD | pip install hedra[statsd] | aio_statsd |\n| TimescaleDB | pip install hedra[sql] | aiopg, psycopg2-binary, sqlalchemy |\n| XML | pip install hedra[xml] | dicttoxml |\n\n<br/>\n\n___________\n\n## <b>Resources</b>\n\nHedra's official and full documentation is currently being written and will be linked here soon!\n\n___________\n\n## <b>License</b>\n\nThis software is licensed under the MIT License. See the LICENSE file in the top distribution directory for the full license text.\n\n___________\n\n## <b>Contributing</b>\n\nHedra will be open to general contributions starting Fall, 2023 (once the distributed rewrite and general testing is complete). Until then, feel\nfree to use Hedra on your local machine and report any bugs or issues you find!\n\n___________\n\n## <b>Code of Conduct</b>\n\nHedra has adopted and follows the [Contributor Covenant code of conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md).\nIf you observe behavior that violates those rules please report to:\n\n| Name | Email | Twitter |\n|------- |-------- |---------- |\n| Sean Corbett | sean.corbett@umontana.edu | [@sc_codeum](https://twitter.com/sc_codeUM/) |\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2022 scorbettUM Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "Performance testing at scale.",
"version": "0.7.24",
"project_urls": {
"Homepage": "https://github.com/adalundhe/hedra"
},
"split_keywords": [
"pypi",
" cicd",
" python",
" performance",
" testing",
" dag",
" graph",
" workflow"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "35849210e85c713982ad35225387acb80d3632774e8c74e53dac55e952896dff",
"md5": "b8e4318c6e05583c56acd64699a401f2",
"sha256": "d5b8b0ea0d5eb872dd20b8bd2fe1df62f67a0fd4730d75ea7b9a5893cc9f37f6"
},
"downloads": -1,
"filename": "hedra-0.7.24-py3-none-any.whl",
"has_sig": false,
"md5_digest": "b8e4318c6e05583c56acd64699a401f2",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 962558,
"upload_time": "2024-10-30T00:20:22",
"upload_time_iso_8601": "2024-10-30T00:20:22.244367Z",
"url": "https://files.pythonhosted.org/packages/35/84/9210e85c713982ad35225387acb80d3632774e8c74e53dac55e952896dff/hedra-0.7.24-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "dbf4c821caff9cc8cb449e6b722e335aa8f0e68e9ff6a8f58b8fa98105feee29",
"md5": "e4f20615a101fcd0e750e5a148beb23c",
"sha256": "5dd9d9bc6b7637cdcf8fd8f7178b226053fdf4edeb075daffc7bf11d20562dec"
},
"downloads": -1,
"filename": "hedra-0.7.24.tar.gz",
"has_sig": false,
"md5_digest": "e4f20615a101fcd0e750e5a148beb23c",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 516719,
"upload_time": "2024-10-30T00:20:24",
"upload_time_iso_8601": "2024-10-30T00:20:24.514355Z",
"url": "https://files.pythonhosted.org/packages/db/f4/c821caff9cc8cb449e6b722e335aa8f0e68e9ff6a8f58b8fa98105feee29/hedra-0.7.24.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-10-30 00:20:24",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "adalundhe",
"github_project": "hedra",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "hedra"
}
