adding reference to the load testing use case in the documentation

This commit is contained in:
Julien Neuhart
2019-09-30 17:19:14 +02:00
parent 9968a816db
commit 3d379dec58
2 changed files with 6 additions and 0 deletions

View File

@@ -14,6 +14,8 @@ The more concurrent requests, the more `504` HTTP codes the API will return.
On another hand, for [Office](#office) conversions, the API will start as many unoconv (LibreOffice) instances as there are
requests. The limitation here is the available memory.
> See our [load testing use case](../loadtesting) for more details about the API behaviour under heavy load.
## Strategies
### Increase timeout

View File

@@ -1321,6 +1321,10 @@ The more concurrent requests, the more <code>504</code> HTTP codes the API will
<p>On another hand, for <a href="#office">Office</a> conversions, the API will start as many unoconv (LibreOffice) instances as there are
requests. The limitation here is the available memory.</p>
<blockquote>
<p>See our <a href="../loadtesting">load testing use case</a> for more details about the API behaviour under heavy load.</p>
</blockquote>
<h2 class="Heading"><a class="Anchor" aria-hidden="true" id="scalability.strategies" href="#scalability.strategies">
<svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather feather-link"><path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71"></path><path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71"></path></svg>
</a>Strategies</h2>