-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
- Loading branch information
There are no files selected for viewing
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HowTo on Hyperfoil</title><link>https://hyperfoil.io/categories/howto/</link><description>Recent content in HowTo on Hyperfoil</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://hyperfoil.io/categories/howto/index.xml" rel="self" type="application/rss+xml"/><item><title>Benchmark schema support</title><link>https://hyperfoil.io/docs/howtos/editor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/editor/</guid><description>For your convenience we recommend using editor with YAML validation against JSON schema; you can point your editor to docs/schema.json. We can recommend Visual Studio Code with redhat.vscode-yaml plugin. | ||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HowTo on Hyperfoil</title><link>https://hyperfoil.io/categories/howto/</link><description>Recent content in HowTo on Hyperfoil</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://hyperfoil.io/categories/howto/index.xml" rel="self" type="application/rss+xml"/><item><title>JSON schema support</title><link>https://hyperfoil.io/docs/howtos/editor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/editor/</guid><description>For your convenience we recommend using editor with YAML validation against JSON schema; you can point your editor to docs/schema.json. We can recommend Visual Studio Code with redhat.vscode-yaml plugin. | ||
You need to edit settings file to map benchmark configuration files (with .hf.yaml extension) to the schema, adding: | ||
&#34;yaml.schemas&#34; : { &#34;file:///path/to/hyperfoil-distribution/docs/schema.json&#34; : &#34;/*.hf.yaml&#34; }, Note that you can also directly point to the hosted JSON schema definition: | ||
&#34;yaml.schemas&#34; : { &#34;https://hyperfoil.</description></item><item><title>Using credentials</title><link>https://hyperfoil.io/docs/howtos/credentials/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/credentials/</guid><description>Hyperfoil benchmarks can refer to external files. When you use the upload command in CLI the files are automatically attached the the benchmark YAML (relative paths are resolved relative to this file). Later on when editing the file you can choose to re-upload some of these. Once the benchmark is built the files are loaded to the in-memory representation - Hyperfoil won&rsquo;t access these files during runtime. With clustered benchmarks these files don&rsquo;t need to be on the agents either - the controller sends serialized in-memory representation to the agents and that contains everything needed for the actual execution.</description></item><item><title>How To</title><link>https://hyperfoil.io/docs/howtos/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/</guid><description>This section contains practical advices for common things you could want to use in a benchmark.</description></item></channel></rss> | ||
&#34;yaml.schemas&#34; : { &#34;https://hyperfoil.</description></item><item><title>Using credentials</title><link>https://hyperfoil.io/docs/howtos/credentials/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/credentials/</guid><description>Hyperfoil benchmarks can refer to external files. When you use the upload command in CLI the files are automatically attached the the benchmark YAML (relative paths are resolved relative to this file). Later on when editing the file you can choose to re-upload some of these. Once the benchmark is built the files are loaded to the in-memory representation - Hyperfoil won&rsquo;t access these files during runtime. With clustered benchmarks these files don&rsquo;t need to be on the agents either - the controller sends serialized in-memory representation to the agents and that contains everything needed for the actual execution.</description></item><item><title>Hyperfoil run script</title><link>https://hyperfoil.io/docs/howtos/run_scripts/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/run_scripts/</guid><description>Starting from release 0.27, Hyperfoil includes an easy-to-use script that simplifies running benchmarks, allowing users to try tests faster when in-vm controller server is acceptable. | ||
This script is particularly beneficial when you need to quickly test, validate or refine your benchmark definitions, ensuring they run as expected without needing to manually orchestrate the controller and agent processes. It also enables seamless integration into automation scripts or CI/CD pipelines, where you can configure benchmarks to run as part of routine testing, with results saved for further analysis.</description></item><item><title>How To</title><link>https://hyperfoil.io/docs/howtos/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/</guid><description>This section contains practical advices for common things you could want to use in a benchmark.</description></item></channel></rss> |
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How To on Hyperfoil</title><link>https://hyperfoil.io/docs/howtos/</link><description>Recent content in How To on Hyperfoil</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://hyperfoil.io/docs/howtos/index.xml" rel="self" type="application/rss+xml"/><item><title>Benchmark schema support</title><link>https://hyperfoil.io/docs/howtos/editor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/editor/</guid><description>For your convenience we recommend using editor with YAML validation against JSON schema; you can point your editor to docs/schema.json. We can recommend Visual Studio Code with redhat.vscode-yaml plugin. | ||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How To on Hyperfoil</title><link>https://hyperfoil.io/docs/howtos/</link><description>Recent content in How To on Hyperfoil</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://hyperfoil.io/docs/howtos/index.xml" rel="self" type="application/rss+xml"/><item><title>JSON schema support</title><link>https://hyperfoil.io/docs/howtos/editor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/editor/</guid><description>For your convenience we recommend using editor with YAML validation against JSON schema; you can point your editor to docs/schema.json. We can recommend Visual Studio Code with redhat.vscode-yaml plugin. | ||
You need to edit settings file to map benchmark configuration files (with .hf.yaml extension) to the schema, adding: | ||
&#34;yaml.schemas&#34; : { &#34;file:///path/to/hyperfoil-distribution/docs/schema.json&#34; : &#34;/*.hf.yaml&#34; }, Note that you can also directly point to the hosted JSON schema definition: | ||
&#34;yaml.schemas&#34; : { &#34;https://hyperfoil.</description></item><item><title>Using credentials</title><link>https://hyperfoil.io/docs/howtos/credentials/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/credentials/</guid><description>Hyperfoil benchmarks can refer to external files. When you use the upload command in CLI the files are automatically attached the the benchmark YAML (relative paths are resolved relative to this file). Later on when editing the file you can choose to re-upload some of these. Once the benchmark is built the files are loaded to the in-memory representation - Hyperfoil won&rsquo;t access these files during runtime. With clustered benchmarks these files don&rsquo;t need to be on the agents either - the controller sends serialized in-memory representation to the agents and that contains everything needed for the actual execution.</description></item></channel></rss> | ||
&#34;yaml.schemas&#34; : { &#34;https://hyperfoil.</description></item><item><title>Using credentials</title><link>https://hyperfoil.io/docs/howtos/credentials/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/credentials/</guid><description>Hyperfoil benchmarks can refer to external files. When you use the upload command in CLI the files are automatically attached the the benchmark YAML (relative paths are resolved relative to this file). Later on when editing the file you can choose to re-upload some of these. Once the benchmark is built the files are loaded to the in-memory representation - Hyperfoil won&rsquo;t access these files during runtime. With clustered benchmarks these files don&rsquo;t need to be on the agents either - the controller sends serialized in-memory representation to the agents and that contains everything needed for the actual execution.</description></item><item><title>Hyperfoil run script</title><link>https://hyperfoil.io/docs/howtos/run_scripts/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hyperfoil.io/docs/howtos/run_scripts/</guid><description>Starting from release 0.27, Hyperfoil includes an easy-to-use script that simplifies running benchmarks, allowing users to try tests faster when in-vm controller server is acceptable. | ||
This script is particularly beneficial when you need to quickly test, validate or refine your benchmark definitions, ensuring they run as expected without needing to manually orchestrate the controller and agent processes. It also enables seamless integration into automation scripts or CI/CD pipelines, where you can configure benchmarks to run as part of routine testing, with results saved for further analysis.</description></item></channel></rss> |
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.