<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,</p>
<p>Ok - I see - the QGIS-Server-PerfSuite, goal is always sequential
rendering, with no parallel requests - makes sense.</p>
<p>In the Solothurn benchmark we have a docker swarm (or
alternatively kubernetes) setup with parallel requests. But of
course, as you have noted, there are other configuration options
that are not directly QGIS server related. We also wanted to find
out what a useful configuration for parallel requests is. But
there are also overlaps of both benchmarks.<br>
</p>
<p>Thanks for the clarification,</p>
<p>Andreas<br>
</p>
<div class="moz-cite-prefix">Am 13.11.20 um 16:12 schrieb Paul
Blottiere:<br>
</div>
<blockquote type="cite"
cite="mid:CAOWtUUNU_V-2M3CxJwvAjbWuPDrDQXS6MvUS3Vj6W7fREy3Vig@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">Hi Andreas,<br>
<br>
> Paul: can you clarify if you tested "sequentially"
without parallel requests? To me, if I interpret it correctly,
this seems to be the case here. Are you doing 20 subsequent,
sequential, requests?<br>
<br>
Yes there aren't scenarios with parallel requests. As soon as
you have parallel requests, you need several QGIS Server
instances and a load balancer (because a QGIS Server instance
is able to address 1 request at a time). So in this case, you
don't test the nominal behavior of QGIS Server, but the
response time of the whole "infrastructure".<br>
<br>
And in case of the QGIS-Server-PerfSuite, we want to check the
rendering time for a specific request.<br>
<br>
<br>
> In the Solothurn benchmarks that Marco did, we almost
always did parallel requests - and we found out that the
threaded rendering slows down rendering if you have a lot of
parallel requests, whereas, if you have no or only 2-3
parallel requests, the threaded rendering is faster. In
general, in reality we often have 5-15 parallel requests in
our organization in Solothurn.<br>
<br>
If you have too many instances of QGIS Server with the
parallel rendering activated, then you won't necessarily have
enough cores to process the rendering efficiently in case of
parallel requests. In this case, it may even lead to
performance issues but it's not an issue with QGIS Server
itself.<br>
</div>
<div dir="ltr"><br>
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr"><br>
</div>
<div class="gmail_attr">Regards.</div>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div dir="ltr">Paul Blottiere</div>
<div>QCooperative: <a href="https://www.qcooperative.net/"
target="_blank" moz-do-not-send="true">https://www.qcooperative.net/</a></div>
<div>Hytech Imaging: <a href="https://hytech-imaging.fr/"
target="_blank" moz-do-not-send="true">https://hytech-imaging.fr/</a></div>
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>