[mapguide-users] Mapguide 2.5 poor performances on a multicore environment
Jackie Ng
jumpinjackie at gmail.com
Fri Oct 13 08:34:35 PDT 2017
If FDO trace logging doesn't work for you, PostgreSQL should have some
logging facility where you can enable to see all SQL statements executed.
Perhaps something like this:
https://stackoverflow.com/questions/8208310/postgresql-how-to-see-which-queries-have-run
The idea is, if you are able to see the bottlenecked rendering, that we are
able to capture all the SQL statements that were executed, and then be able
to run such queries in isolation and if we can verify certain queries being
slow, to then use pgAdmin to EXPLAIN these queries.
>From the EXPLAIN'ed execution plans you can then see if it is indeed hitting
your spatial and secondary indexes or if it is doing something terrible like
table scans.
For the record, I'm not a PostgreSQL expert. My main day-to-day RDBMS is
Microsoft SQL Server, but any RDBMS worth their salt will have built-in
facilities to log/capture SQL statement execution and produce execution
plans on any query.
- Jackie
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
More information about the mapguide-users
mailing list