Optimizing tile generation + question about extent

[sanderpukk]

Hi!

Generating tiles in cloudservices. For this example, let's say it's Azure's 72 node and 144 GB of RAM machine.

First the performance. The documentation is a little lacking in that part. We are using Postgres as a source. Now, how would I approach the needed nodes for t-rex and the nodes for postgres?

• Am I supposed to use (72/2)-1 nodes for t-rex and the rest for postgres?
• What does that "pool" parameter actually do in your documentation?
• Besides functionality, is Postgres connection the most optimal? Are GPKG better for performance?

A better documentation for performance would be much appreciated.

Second point: When using custom grid and extent and extent in tileset, it does clip accordingly. But when using built in web_mercator grid, the extent is confusing.

Tileset extent in your github examples is an array of coordinates. BottomLeft to RightTop. But in the webpage documentation it's a json extent: { minx: float, miny: float, maxx: float, maxy: float }. Same as for user grid.

The thing is, if I use grid.user with my extent and the same value in tileset, it does clip. Webmercator doesnt seem to work like that. What is the correct way?

[sanderpukk]

Did not wanna sound too negative. I like using t-rex and the toml approach. Really versatile :)