For reference, one query which took 10 seconds before now takes 6 seconds. The only change was to upgrade PostGIS and PostgreSQL. And this isn't using all the cool new-ish parallel processing.https://twitter.com/robhawkes/status/1139114417025638400 …
-
-
That's great to hear! Can you shed some light on what the right conditions are? That aspect of parallelisation is still a bit like magic to me right now.
-
Mostly it’s tied to the number of rows going into the function. (Also, you have to set your various postgresql.conf variables to actually turn it on). https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PARALLEL-WORKERS-PER-GATHER …
End of conversation
New conversation -
-
-
Parallel ST_ AsMVT was included in 2.5, but 3.0 includes wagyu to process polygons, faster column processing (only noticebale with dozens/hundreds of columns) and some other microptimizations

-
I'm yet to see ST_AsMVT use a parallel plan so curious what I'm doing wrong. It must be the wagyu improvements that I'm seeing; it's a big improvement!
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.