Opened 5 months ago

Last modified 4 months ago

#4490 assigned enhancement

PG12: Review MVT functions cost

Reported by: Algunenano Owned by: Algunenano
Priority: medium Milestone: PostGIS 3.1.0
Component: postgis Version: master
Keywords: Cc:


The current cost (`procost+ ) of ST_AsMVTGeom is the C default (1). Since it's a function that can have a really high CPU usage we should consider raising its cost to improve parallelization.

I think we should review it together with the ST_AsMVT, since they are usually called together and the aggregation might also have a high cost (depends on the how the hash table is populated).

Change History (4)

comment:1 Changed 5 months ago by Algunenano

The only function without cost is ST_AsMVTGeom; all other function (related to ST_AsMVT aggregate) have _COST_MEDIUM setup.

I think setting ST_AsMVTGeom to _COST_HIGH should be ok, but I'll do some tests to see if there is some big difference a performance framework.

comment:2 Changed 4 months ago by pramsey

Results? Seems reasonable to me.

comment:3 Changed 4 months ago by pramsey

Running up against deadline here.

comment:4 Changed 4 months ago by Algunenano

Milestone: PostGIS 3.0.0PostGIS 3.1.0

I'm not having as much time as I'd like to test this properly, so I'd rather move it back to 3.0.1 or 3.1

Note: See TracTickets for help on using tickets.