Debugging PostgreSQL performance issues #1219
Replies: 3 comments
-
|
I tried to dig a bit into the whole performance situation and used the pg_stat_statements extension to check which queries take up the most time: SELECT calls, round(total_exec_time) AS total_exec, round(mean_exec_time) as mean_exec, round(jit_generation_time) as jit_generation, round(jit_inlining_time) as jit_inlining, round(jit_emission_time) as jit_emission, jit_optimization_count, query FROM public.pg_stat_statements
ORDER BY total_exec_time DESC
LIMIT 7After a short while this is the timing information (in milliseconds) I got: |
Beta Was this translation helpful? Give feedback.
-
|
So the only statement that causes problems seems to be text searches on CourseMapper-webserver/coursemapper-kg/preprocess/src/database.py Lines 44 to 45 in 1092da6 |
Beta Was this translation helpful? Give feedback.
-
|
In development In production So the only index present in production is the primary key. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
To help debugging issue #1212, the following pgAdmin UI are (temporarily) available:
I'll try to find out what causes the high load, but I'm not exactly an expert in PostgreSQL. @rawaa123 Please let me know, if you need any particular extensions/settings for performance profiling.
Beta Was this translation helpful? Give feedback.
All reactions