![]() Other improvements that also benefit us are speed ups in ST_Simplify or ST_RemoveRepeatedPoints which are used when rendering raster images or preprocessing geometries for further analysis.Īs an example of this improved performance we released this functionality on July 1st on our platform. One function that has seen its performance increased by more than an order of magnitude is ST_AsMVTGeom which is the internal function CARTO uses to create vector tiles. Now with better adjustment on PostGIS in terms of function costs parallelization should trigger much more. PostgreSQL 12.0 has also enabled better parallelization of functions in extensions like PostGIS. Speed Increases in PostGIS come in two flavors - Speeding up the actual functions and ensuring that they can run in parallel on PostgreSQL. You can find the full release notes here but we wanted to highlight some of the key areas that we are most excited about. This release comes with a lot of enhancements bug fixes and several new features. Still it is a huge moment of celebration when all of this functionality goes into a public release.ģ.0 has been a moderately large release in terms of the amount of changes with over 150 issues addressed and CARTO has worked on at least 74 of them. We run a custom version of PostGIS that is ahead of the release cycle which ensures that our users always have the fastest service possible. ![]() If you are a CARTO user you have actually been using PostGIS 3.0.0 features for a long time. So for CARTO and our clients the 3.0 release is a big milestone! In fact when it comes to contributing to PostGIS we are the most active organization working on the project. Most of our users are aware that under the hood CARTO runs on PostgreSQL and PostGIS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |