<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 3/20/2018 1:40 PM, sav123 wrote:<br>
</div>
<blockquote type="cite"
cite="mid:E5E9D0522DBF48BBB53E47F74E4F063B@sav4PC">
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">Kompza covered
the variables you mentioned, but I if you're looking at
<br>
</blockquote>
</blockquote>
benchmarking, I recommend you set up the full rendering stack
rather
<br>
than trying to generate queries yourself. The latter can be tricky
to
<br>
get right, and you have to handle parallelism the same as the full
stack
<br>
to get meaningful results. It's just easier to use renderd and
feed it a
<br>
list of tiles with render_list than to write code that will take
that
<br>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">list, generate
SQL, and run it.
<br>
</blockquote>
</blockquote>
<br>
This doesn't answer the question.
<br>
If you read the carto file, you will see that there are natural
criteria , not only geometry.
<br>
Indeed, it is a bad idea to partition on coordinates, unless if a
request applies to a small region.
</blockquote>
<br>
I'm not speaking of partitioning, but of how to best benchmark
performance, which is what you're planning to do to see if
partitioning is worthwhile.<br>
</body>
</html>