The problem is geojson probably. geojson is a very inefficient format.
You cannot use that with success for more than a small number of
geometries.
It is a text format, and quite heavy to build.
I don't think you will find any software building a million geometries
of geojson very fast, I am afraid.
The result will also be a nightmare to use for rendering.
So, I think the issue is the choice of format.
What is the use case?
/Nicklas
On Thu, 2017-09-21 at 15:10 +0530, Pradeep Kanth G wrote:
> Hi Nicklas,
>
> I have around 300 feature classes and each feature class having more
> than 1 million of rows. While querying with spatial
> functions(StGeoJson, Intersection etc..) it’s taking lot of time and
> also created spatial indexes on those layers.
> So kindly let me know ,how to overcome this issue.
>
>
> Regards
> Pradeep Kanth
>
> From: postgis-users [mailto:[email protected]] On
> Behalf Of Nicklas Avén
> Sent: Thursday, September 21, 2017 2:10 PM
> To: PostGIS Users Discussion <[email protected]>
> Subject: Re: [postgis-users] PostgreSQL VS EDB performance with
> PostGIS
>
> Hello
>
> This question is not possible to answer without more information
> like:
>
> Did you have performance problems with PostGIS under PostgreSQL?
> Why do you expect better performance from moving to EDB? What
> functionality in EDB did you expect to impact the performance?
>
> What is the query that is slow? There are many functions in PostGIS,
> what are you using. Most performance problems with PostGIS is related
> to not having indexes where needed, or a query written in a way so
> PostGIS cannot gain from indexes.
>
> Regards
>
> Nicklas
>
> On Thu, 2017-09-21 at 09:20 +0530, Pradeep Kanth G wrote:
> Hi,
>
> Recently , I have moved my PostGIS Spatial data from PostgreSQL to
> EDB(Enterprise DB) .After moving into EDB there is no much difference
> between Open Source PostgreSQL performance wise.
> So kindly suggested to us ,how to improve the EDB performance with
> PostGIS.
>
> Regards
> Pradeep Kanth
>
>
>
> Disclaimer | The information contained in this electronic message
> (including any attachments) is intended for the exclusive use of the
> addressee(s) and may contain confidential or privileged
> information.If you have received this in error, please notify the
> sender immediately and delete the material from your machine. Any
> action including review, retransmission, dissemination of this email
> or the attachments present along with the email by persons or
> entities other than the intended recipient is prohibited.
>
>
>
> _______________________________________________postgis-users mailing
> [email protected]https://lists.osgeo.org/mailman/list
> info/postgis-users
>
>
>
>
> Disclaimer | The information contained in this electronic message
> (including any attachments) is intended for the exclusive use of the
> addressee(s) and may contain confidential or privileged
> information.If you have received this in error, please notify the
> sender immediately and delete the material from your machine. Any
> action including review, retransmission, dissemination of this email
> or the attachments present along with the email by persons or
> entities other than the intended recipient is prohibited.
>
>
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/postgis-users
