Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issue #424

Open
kayform opened this issue Oct 20, 2023 · 3 comments
Open

Performance issue #424

kayform opened this issue Oct 20, 2023 · 3 comments

Comments

@kayform
Copy link

kayform commented Oct 20, 2023

I recently installed pg_stat_monitor to find top queries,
and after executing 'create extension pg_stat_monitor;' and then running 'select * from pg_stat_monitor;', I
noticed that the DBMS became significantly slower, with all sessions appearing to be affected.
The parameters of pg_stat_monitor are in their default state.

environment

OS : aws amazon linux
RAM : 64GB
CPU : 32 core
postgresql 14.5
pg_stat_monitor 2.0.2
parameter : pg_stat_monitor default
The data capacity is approximately 7TB
500 TPS based on the pg_stat_database

@unikzforce
Copy link

so in the end was that really a performance issue created by pg_stat_monitor, or it was something else?

@MichaelDBA
Copy link

Also interested in reply...

@artemgavrilov
Copy link
Contributor

Hello @kayform , one of the things that can cause performance degradation for setups with big number of connections is application name tracking. We just released PGSM v2.1.0 that allows to disable app name tracking, see docs: https://docs.percona.com/pg-stat-monitor/configuration.html#pg_stat_monitorpgsm_track_application_names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants