@SaurabhUpadhyaya -
You need to provide a lot more details, the versions of ArcGIS Pro and ArcGIS Server, the version of PostgreSQL and PostGIS, how you published the Services using the PostgreSQL database (No Geodatabase), how many layers were published together, the number of rows of each layer, etc, etc.
But here are a few tips.
1. Tune your map documents in ArcGIS Pro before you publish, need to add the reference scales to render the layers, also see the symbology, and if using attributes to drive symbology then make sure those layers have the columns indexed, same if using definition queries and/or Query Layers.
2. Identify which Map Service is slow then add to ArcGIS Pro and then trace the https request to see exactly where it is slow. Is slow because the ArcGIS Server number of SOC processes is low? or Is slow because of the PostgreSQL database?
3. If it is the PostgreSQL database then increase the number of connections in the PostgreSQL configuration file, check the PostgreSQL server cpu, memory, disk, network utilization, if normal then the next steps is to do a database tracing in PostgreSQL to capture the SQL statements of the slow Map Service, then analyze the SQL statements to find which SQL or SQL's are slow and then tune the SQL's to improve performance.
4. Perform regular PostgreSQL database maintenance, e.g. vacuum, gather new statistics, rebuild indexes.
5. Keep PostgreSQL and PostGIS updated with the latest patches.
community.esri.com - How to Upgrade the PostgreSQL and PostGIS version for the Enterprise Geodatabase
I hope this helps.
| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov