Ngawasi kinerja pitakon PostgreSQL. Part 1 - nglaporake

Engineer - diterjemahake saka basa Latin - inspirasi.
Insinyur bisa nindakake apa wae. (c) R. Diesel.
Epigraf.

Utawa crita babagan kenapa administrator basis data kudu ngelingi masa lalu pemrograman.

Pambuka

Kabeh jeneng wis diganti. Kebeneran iku acak. Materi kasebut mung pendapat pribadi saka penulis.

Penafian jaminan: ing seri artikel sing direncanakake ora bakal ana katrangan sing rinci lan akurat babagan tabel lan skrip sing digunakake. Materi ora bisa langsung digunakake "AS IS".
Kaping pisanan, amarga akeh materi,
sareh, amarga saka ketajaman karo basis produksi saka customer nyata.
Mulane, mung gagasan lan deskripsi ing wangun sing paling umum bakal diwenehake ing artikel kasebut.
Mungkin ing mangsa ngarep sistem bakal tuwuh nganti tingkat posting ing GitHub, utawa bisa uga ora. Wektu bakal nuduhake.

Wiwitane crita-Apa sampeyan kelingan carane iku kabeh diwiwiti".
Apa sing kedadeyan minangka asil, ing istilah sing paling umum - "Sintesis minangka salah sawijining cara kanggo ningkatake kinerja PostgreSQL»

Napa aku butuh kabeh iki?

Inggih, pisanan, supaya ora lali dhewe, ngelingi dina mulya ing pensiun.
Kapindho, kanggo sistematis apa sing ditulis. Kanggo aku dhewe, kadhangkala aku wiwit bingung lan lali bagean sing kapisah.

Inggih, lan sing paling Jahwéh - dumadakan bisa teka ing Handy kanggo wong lan bantuan ora reinvent setir lan ora kanggo ngumpulake rake. Ing tembung liyane, nambah karma (ora Khabrovsky). Kanggo bab sing paling larang ing donya iki gagasan. Sing utama yaiku golek ide. Lan nerjemahake ide kasebut dadi kasunyatan wis dadi masalah teknis.

Dadi ayo miwiti alon-alon ...

Formulasi masalah.

kasedhiya:

PostgreSQL (10.5), beban campuran (OLTP+DSS), beban medium nganti entheng, di-host ing awan AWS.
Ora ana pemantauan basis data, pemantauan infrastruktur ditampilake minangka alat AWS standar ing konfigurasi minimal.

Dibutuhake:

Ngawasi kinerja lan status database, golek lan duwe informasi awal kanggo ngoptimalake pitakon database abot.

introduksi Brief utawa analisis opsi solusi

Kanggo miwiti, ayo nyoba nganalisa pilihan kanggo ngrampungake masalah kasebut saka sudut pandang analisis komparatif babagan keuntungan lan masalah kanggo insinyur, lan supaya wong-wong sing kudu ana ing dhaptar staf menehi hasil lan kerugian. saka manajemen.

Opsi 1 - "Nggarap panjaluk"

Kita ninggalake kabeh kaya sing dikarepake. Yen customer ora wareg karo soko ing kesehatan, kinerja database utawa aplikasi, bakal ngabari engineers DBA dening e-mail utawa nggawe kedadean ing kothak tiket.
Insinyur, sawise nampa kabar, bakal ngerti masalah kasebut, menehi solusi, utawa ngilangi masalah kasebut, ngarep-arep kabeh bakal rampung dhewe, lan kabeh bakal lali.
Gingerbread lan donat, bruises lan bumpsGingerbread lan donat:
1. Boten ekstra apa
2. Ana tansah kesempatan kanggo metu lan njaluk reged.
3. Akeh wektu sing bisa digunakake dhewe.
Bruises lan benjolan:
1. Cepet utawa mengko, pelanggan bakal mikir babagan hakekat lan keadilan universal ing jagad iki lan sepisan maneh takon dhewe - kenapa aku mbayar dhuwit? Akibate tansah padha - mung pitakonan nalika customer bosen lan waved pamit. Lan feeder kosong. Sedhih.
2. Pangembangan insinyur nol.
3. Kesulitan ing jadwal karya lan loading

Opsi 2 - "Tari nganggo rebana, nganggo lan nganggo sepatu"

Paragraf 1-Apa kita kudu sistem ngawasi, kita bakal nampa kabeh panjalukan. Kita miwiti macem-macem pitakon menyang kamus data lan tampilan dinamis, ngaktifake kabeh jinis counter, nggawa kabeh menyang tabel, nganalisa dhaptar lan tabel kanthi periodik. Akibaté, kita duwe ayu utawa ora banget grafik, tabel, laporan. Wangsulan: Bab ingkang utama - sing bakal luwih, liyane.
Paragraf 2-Generate kegiatan-mbukak analisis kabeh iki.
Paragraf 3-We are nyepakaké document tartamtu, kita nelpon document iki, mung - "carane kita nglengkapi database."
Paragraf 4- Pelanggan, ndeleng kabeh keagungan grafik lan tokoh iki, ana ing kapercayan naif bocah - saiki kabeh bakal bisa digunakake kanggo kita, rauh. Lan, kanthi gampang lan tanpa rasa lara karo sumber daya finansial. Manajemen uga yakin manawa insinyur kita kerja keras. Max loading.
Paragraf 5- Baleni langkah 1 kanthi rutin.
Gingerbread lan donat, bruises lan bumpsGingerbread lan donat:
1. Urip manajer lan insinyur iku prasaja, bisa diprediksi lan diisi karo kegiatan. Kabeh rame, kabeh sibuk.
2. Uripe pelanggan uga ora ala - dheweke mesthi yakin yen sampeyan kudu sabar sethithik lan kabeh bakal bisa ditindakake. Ora dadi luwih apik, wah, - donya iki ora adil, ing urip sabanjuré - sampeyan bakal begja.
Bruises lan benjolan:
1. Cepet utawa mengko, bakal ana panyedhiya layanan sing luwih cepet sing bakal nindakake perkara sing padha, nanging luwih murah. Lan yen asil padha, kok mbayar luwih. Kang maneh bakal mimpin kanggo ilang feeder.
2. Iku mboseni. Carane mboseni sembarang kegiatan migunani sethitik.
3. Kaya ing versi sadurunge, ora ana pangembangan. Nanging kanggo insinyur, kekurangane yaiku, ora kaya pilihan pisanan, sampeyan kudu terus-terusan ngasilake IBD. Lan iki mbutuhake wektu. Sing bisa sampeyan gunakake kanggo kepentingan wong sing dikasihi. Amarga sampeyan ora bisa ngurus dhewe, ora ana sing peduli karo sampeyan.

Opsi 3 - Sampeyan ora perlu nggawe sepedha, sampeyan mung kudu tuku lan numpak.

Iku ora kanggo apa-apa sing engineers saka perusahaan liyane mangan pizza karo bir (oh, dina kamulyan St. Petersburg ing 90s). Ayo nggunakake sistem pemantauan sing digawe, didebug lan digunakake, lan umume entuk manfaat (paling ora kanggo sing nggawe).
Gingerbread lan donat, bruises lan bumpsGingerbread lan donat:
1. Ora perlu mbuwang wektu kanggo nyipta apa sing wis diciptakake. Njupuk lan gunakake.
2. Sistem ngawasi ora ditulis dening wong bodho, lan mesthi migunani.
3. Sistem ngawasi kerja biasane nyedhiyakake informasi sing disaring sing migunani.
Bruises lan benjolan:
1. Insinyur ing kasus iki dudu insinyur, nanging mung pangguna produk wong liya, utawa pangguna.
2. Customer kudu nggawe percoyo saka perlu kanggo tuku soko sing umume ora pengin ngerti, lan ora, lan ing umum budget kanggo taun wis disetujoni lan ora bakal ngganti. Banjur sampeyan kudu nyedhiyakake sumber daya sing kapisah, ngatur kanggo sistem tartamtu. Sing. Pisanan sampeyan kudu mbayar, mbayar lan mbayar maneh. Lan pelanggan iku pelit. Iki minangka norma urip iki.

Apa sing kudu ditindakake, Chernyshevsky? Pitakonan sampeyan cocog banget. (karo)

Ing kasus tartamtu lan kahanan saiki, sampeyan bisa nindakake sing rada beda - ayo gawe sistem monitoring dhewe.

Inggih, dudu sistem, mesthi, ing pangertèn lengkap tembung, iki banter banget lan presumptuous, nanging paling piye wae nggawe luwih gampang kanggo dhewe lan ngumpulake informasi liyane kanggo ngatasi kedadean kinerja. Supaya ora nemokake dhewe ing kahanan - "menyang kana, aku ora ngerti ngendi, golek sing, aku ora ngerti apa."

Apa pro lan kontra saka pilihan iki:

Pros:
1. Iku menarik. Ya, paling ora luwih menarik tinimbang "file data nyusut, ngowahi tablespace, lan liya-liyane."
2. Iki minangka katrampilan anyar lan pangembangan anyar. Sing ing mangsa ngarep, cepet utawa mengko, bakal menehi roti jahe lan donat sing pantes.
Cons:
1. Kudu nyambut gawe. Kerjo akeh.
2. Sampeyan kudu ajeg nerangake makna lan perspektif kabeh kegiatan.
3. Ana sing kudu dikorbanake, amarga mung sumber daya sing kasedhiya kanggo insinyur - wektu - diwatesi dening Semesta.
4. Sing paling awon lan paling ora nyenengake - Akibaté, sampah kaya "Ora tikus, dudu kodhok, nanging kewan cilik sing ora dingerteni" bisa uga.

Sing ora njupuk risiko ora ngombe sampanye.
Dadi, kesenengan diwiwiti.

Ide umum - skema

(Ilustrasi dijupuk saka artikel «Sintesis minangka salah sawijining cara kanggo ningkatake kinerja PostgreSQL»)

Panjelasan:

• Basis data target diinstal nganggo ekstensi PostgreSQL standar "pg_stat_statements".
• Ing basis data pemantauan, kita nggawe set tabel layanan kanggo nyimpen riwayat pg_stat_statements ing tahap wiwitan lan kanggo ngatur metrik lan ngawasi ing mangsa ngarep.
• Ing host ngawasi, kita nggawe set skrip bash, kalebu sing kanggo ngasilake kedadeyan ing sistem tiket.

Tabel layanan

Kanggo miwiti, ERD sing disederhanakake kanthi skematis, apa sing kedadeyan ing pungkasan:

gambaran Brief saka tabelendpoint - inang, titik sambungan kanggo Kayata
database - pilihan database
pg_stat_history - tabel sajarah kanggo nyimpen jepretan sauntara tampilan pg_stat_statements saka database target
metric_glossary - Kamus metrik kinerja
metric_config - konfigurasi metrik individu
metrik - metrik khusus kanggo panyuwunan sing dipantau
metric_alert_history - riwayat bebaya kinerja
log_query - Tabel layanan kanggo nyimpen cathetan sing diurai saka file log PostgreSQL sing diundhuh saka AWS
baseline - paramèter saka periode wektu digunakake minangka basis
priksa - konfigurasi metrik kanggo mriksa status database
checkpoint_alert_history - riwayat peringatan babagan metrik mriksa status database
pg_stat_db_queries - Tabel layanan panjalukan aktif
log_aktivitas - Tabel layanan log aktivitas
trap_oid - Tabel layanan konfigurasi trap

Tahap 1 - ngumpulake statistik kinerja lan entuk laporan

Tabel digunakake kanggo nyimpen informasi statistik. pg_stat_history
pg_stat_history struktur tabel

                                          Tabel "public.pg_stat_history" Kolom | jinis | Pengubah ---------------------------- --------------------------------- id | integer | not null default nextval('pg_stat_history_id_seq'::regclass) snapshot_timestamp | stempel wektu tanpa zona wektu | id_database | integer | dbid | oyod | panganggo | oyod | pitakon | agung | pitakon | teks | telpon | agung | total_wektu | tliti kaping pindho | min_wektu | tliti kaping pindho | max_time | tliti kaping pindho | tegese_wektu | tliti kaping pindho | stddev_time | tliti kaping pindho | larik | agung | shared_blks_hit | agung | shared_blks_read | agung | shared_blks_dirtied | agung | shared_blks_written | agung | local_blks_hit | agung | local_blks_read | agung | local_blks_dirtied | agung | local_blks_written | agung | temp_blks_read | agung | temp_blks_written | agung | blk_read_time | tliti kaping pindho | blk_write_time | tliti kaping pindho | id_dasar | integer | Indeks: "pg_stat_history_pkey" KUNCI UTAMA, btree (id) "database_idx" btree (database_id) "queryid_idx" btree (queryid) "snapshot_timestamp_idx" btree (snapshot_timestamp) Foreign-key constraints: ("iddatabase_IDX) ) ING DELETE CASCADE

Nalika sampeyan bisa ndeleng, tabel mung data tampilan kumulatif pg_stat_statements ing basis data target.

Panggunaan tabel iki prasaja banget.

pg_stat_history bakal makili statistik akumulasi eksekusi query kanggo saben jam. Ing awal saben jam, sawise ngisi tabel, statistik pg_stat_statements ngreset karo pg_stat_statements_reset().
Wigati: Statistik diklumpukake kanggo pitakon kanthi durasi eksekusi luwih saka 1 detik.
Isi tabel pg_stat_history

--pg_stat_history.sql
CREATE OR REPLACE FUNCTION pg_stat_history( ) RETURNS boolean AS $$
DECLARE
  endpoint_rec record ;
  database_rec record ;
  pg_stat_snapshot record ;
  current_snapshot_timestamp timestamp without time zone;
BEGIN
  current_snapshot_timestamp = date_trunc('minute',now());  
  
  FOR endpoint_rec IN SELECT * FROM endpoint 
  LOOP
    FOR database_rec IN SELECT * FROM database WHERE endpoint_id = endpoint_rec.id 
	  LOOP
	    
		RAISE NOTICE 'NEW SHAPSHOT IS CREATING';
		
		--Connect to the target DB	  
	    EXECUTE 'SELECT dblink_connect(''LINK1'',''host='||endpoint_rec.host||' dbname='||database_rec.name||' user=USER password=PASSWORD '')';
 
        RAISE NOTICE 'host % and dbname % ',endpoint_rec.host,database_rec.name;
		RAISE NOTICE 'Creating snapshot of pg_stat_statements for database %',database_rec.name;
		
		SELECT 
	      *
		INTO 
		  pg_stat_snapshot
	    FROM dblink('LINK1',
	      'SELECT 
	       dbid , SUM(calls),SUM(total_time),SUM(rows) ,SUM(shared_blks_hit) ,SUM(shared_blks_read) ,SUM(shared_blks_dirtied) ,SUM(shared_blks_written) , 
           SUM(local_blks_hit) , SUM(local_blks_read) , SUM(local_blks_dirtied) , SUM(local_blks_written) , SUM(temp_blks_read) , SUM(temp_blks_written) , SUM(blk_read_time) , SUM(blk_write_time)
	       FROM pg_stat_statements WHERE dbid=(SELECT oid from pg_database where datname=current_database() ) 
		   GROUP BY dbid
  	      '
	               )
	      AS t
	       ( dbid oid , calls bigint , 
  	         total_time double precision , 
	         rows bigint , shared_blks_hit bigint , shared_blks_read bigint ,shared_blks_dirtied bigint ,shared_blks_written	 bigint ,
             local_blks_hit	 bigint ,local_blks_read bigint , local_blks_dirtied bigint ,local_blks_written bigint ,
             temp_blks_read	 bigint ,temp_blks_written bigint ,
             blk_read_time double precision , blk_write_time double precision	  
	       );
		 
		INSERT INTO pg_stat_history
          ( 
		    snapshot_timestamp  ,database_id  ,
			dbid , calls  ,total_time ,
            rows ,shared_blks_hit  ,shared_blks_read  ,shared_blks_dirtied  ,shared_blks_written ,local_blks_hit , 	 	
            local_blks_read,local_blks_dirtied,local_blks_written,temp_blks_read,temp_blks_written, 	
            blk_read_time, blk_write_time 
		  )		  
	    VALUES
	      (
	       current_snapshot_timestamp ,
		   database_rec.id ,
	       pg_stat_snapshot.dbid ,pg_stat_snapshot.calls,
	       pg_stat_snapshot.total_time,
	       pg_stat_snapshot.rows ,pg_stat_snapshot.shared_blks_hit ,pg_stat_snapshot.shared_blks_read ,pg_stat_snapshot.shared_blks_dirtied ,pg_stat_snapshot.shared_blks_written , 
           pg_stat_snapshot.local_blks_hit , pg_stat_snapshot.local_blks_read , pg_stat_snapshot.local_blks_dirtied , pg_stat_snapshot.local_blks_written , 
	       pg_stat_snapshot.temp_blks_read , pg_stat_snapshot.temp_blks_written , pg_stat_snapshot.blk_read_time , pg_stat_snapshot.blk_write_time 	   
	      );		   
		  
        RAISE NOTICE 'Creating snapshot of pg_stat_statements for queries with min_time more than 1000ms';
	
        FOR pg_stat_snapshot IN
          --All queries with max_time greater than 1000 ms
	      SELECT 
	        *
	      FROM dblink('LINK1',
	        'SELECT 
	         dbid , userid ,queryid,query,calls,total_time,min_time ,max_time,mean_time, stddev_time ,rows ,shared_blks_hit ,
			 shared_blks_read ,shared_blks_dirtied ,shared_blks_written , 
             local_blks_hit , local_blks_read , local_blks_dirtied , 
			 local_blks_written , temp_blks_read , temp_blks_written , blk_read_time , 
			 blk_write_time
	         FROM pg_stat_statements 
			 WHERE dbid=(SELECT oid from pg_database where datname=current_database() AND min_time >= 1000 ) 
  	        '

	                  )
	        AS t
	         ( dbid oid , userid oid , queryid bigint ,query text , calls bigint , 
  	           total_time double precision ,min_time double precision	 ,max_time double precision	 , mean_time double precision	 ,  stddev_time double precision	 , 
	           rows bigint , shared_blks_hit bigint , shared_blks_read bigint ,shared_blks_dirtied bigint ,shared_blks_written	 bigint ,
               local_blks_hit	 bigint ,local_blks_read bigint , local_blks_dirtied bigint ,local_blks_written bigint ,
               temp_blks_read	 bigint ,temp_blks_written bigint ,
               blk_read_time double precision , blk_write_time double precision	  
	         )
	    LOOP
		  INSERT INTO pg_stat_history
          ( 
		    snapshot_timestamp  ,database_id  ,
			dbid ,userid  , queryid  , query  , calls  ,total_time ,min_time ,max_time ,mean_time ,stddev_time ,
            rows ,shared_blks_hit  ,shared_blks_read  ,shared_blks_dirtied  ,shared_blks_written ,local_blks_hit , 	 	
            local_blks_read,local_blks_dirtied,local_blks_written,temp_blks_read,temp_blks_written, 	
            blk_read_time, blk_write_time 
		  )		  
	      VALUES
	      (
	       current_snapshot_timestamp ,
		   database_rec.id ,
	       pg_stat_snapshot.dbid ,pg_stat_snapshot.userid ,pg_stat_snapshot.queryid,pg_stat_snapshot.query,pg_stat_snapshot.calls,
	       pg_stat_snapshot.total_time,pg_stat_snapshot.min_time ,pg_stat_snapshot.max_time,pg_stat_snapshot.mean_time, pg_stat_snapshot.stddev_time ,
	       pg_stat_snapshot.rows ,pg_stat_snapshot.shared_blks_hit ,pg_stat_snapshot.shared_blks_read ,pg_stat_snapshot.shared_blks_dirtied ,pg_stat_snapshot.shared_blks_written , 
           pg_stat_snapshot.local_blks_hit , pg_stat_snapshot.local_blks_read , pg_stat_snapshot.local_blks_dirtied , pg_stat_snapshot.local_blks_written , 
	       pg_stat_snapshot.temp_blks_read , pg_stat_snapshot.temp_blks_written , pg_stat_snapshot.blk_read_time , pg_stat_snapshot.blk_write_time 	   
	      );
		  
        END LOOP;

        PERFORM dblink_disconnect('LINK1');  
				
	  END LOOP ;--FOR database_rec IN SELECT * FROM database WHERE endpoint_id = endpoint_rec.id 
    
  END LOOP;

RETURN TRUE;  
END
$$ LANGUAGE plpgsql;

Akibaté, sawise sawetara wektu ing meja pg_stat_history kita bakal duwe pesawat saka jepretan saka isi meja pg_stat_statements database target.

Nyatane laporan

Nggunakake pitakon prasaja, sampeyan bisa entuk laporan sing cukup migunani lan menarik.

Data gabungan kanggo wektu tartamtu

Panjaluk

SELECT 
  database_id , 
  SUM(calls) AS calls ,SUM(total_time)  AS total_time ,
  SUM(rows) AS rows , SUM(shared_blks_hit)  AS shared_blks_hit,
  SUM(shared_blks_read) AS shared_blks_read ,
  SUM(shared_blks_dirtied) AS shared_blks_dirtied,
  SUM(shared_blks_written) AS shared_blks_written , 
  SUM(local_blks_hit) AS local_blks_hit , 
  SUM(local_blks_read) AS local_blks_read , 
  SUM(local_blks_dirtied) AS local_blks_dirtied , 
  SUM(local_blks_written)  AS local_blks_written,
  SUM(temp_blks_read) AS temp_blks_read, 
  SUM(temp_blks_written) temp_blks_written , 
  SUM(blk_read_time) AS blk_read_time , 
  SUM(blk_write_time) AS blk_write_time
FROM 
  pg_stat_history
WHERE 
  queryid IS NULL AND
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY database_id ;

D.B. Wektu

to_char(interval '1 milidetik' * pg_total_stat_history_rec.total_time, 'HH24:MI:SS.MS')

Wektu I/O

to_char(interval '1 milidetik' * ( pg_total_stat_history_rec.blk_read_time + pg_total_stat_history_rec.blk_write_time ), 'HH24:MI:SS.MS')

TOP10 SQL dening total_time

Panjaluk

SELECT 
  queryid , 
  SUM(calls) AS calls ,
  SUM(total_time)  AS total_time  	
FROM 
  pg_stat_history
WHERE 
  queryid IS NOT NULL AND 
  database_id = DATABASE_ID AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT 
GROUP BY queryid 
ORDER BY 3 DESC 
LIMIT 10

--------------------------------------------------- ------------------------------------ | TOP10 SQL Miturut TOTAL EXECUTION TIME | #| pitakon | telpon | telpon %| total_wektu (ms) | dbtime % +----+-----------+-----------+-----------+------ --------------------------+---------- | 1 | 821760255| 2| .00001|00:03:23.141( 203141.681 ms.)| 5.42 | 2| 4152624390| 2| .00001|00:03:13.929( 193929.215 ms.)| 5.17 | 3| 1484454471| 4| .00001|00:02:09.129( 129129.057 ms.)| 3.44 | 4| 655729273| 1 | .00000|00:02:01.869( 121869.981 ms.)| 3.25 | 5| 2460318461| 1 | .00000|00:01:33.113( 93113.835 ms.)| 2.48 | 6| 2194493487| 4| .00001|00:00:17.377( 17377.868 ms.)| .46 | 7| 1053044345| 1 | .00000|00:00:06.156( 6156.352 ms.)| .16 | 8| 3644780286| 1 | .00000|00:00:01.063( 1063.830 ms.)| .03

TOP10 SQL dening total wektu I / O

Panjaluk

SELECT 
  queryid , 
  SUM(calls) AS calls ,
  SUM(blk_read_time + blk_write_time)  AS io_time
FROM 
  pg_stat_history
WHERE 
  queryid IS NOT NULL AND 
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY  queryid 
ORDER BY 3 DESC 
LIMIT 10

--------------------------------------------------- ---------------------------------------------------- | TOP10 SQL Miturut TOTAL I / O TIME | #| pitakon | telpon | telpon %| Wektu I/O (ms)|db wektu I/O % +----+-----------+-----------+------ ----------------+---------- -- | 1 | 4152624390| 2| .00001|00:08:31.616( 511616.592 ms.)| 31.06 Juni | 2| 821760255| 2| .00001|00:08:27.099( 507099.036 ms.)| 30.78 | 3| 655729273| 1 | .00000|00:05:02.209( 302209.137 ms.)| 18.35 | 4| 2460318461| 1 | .00000|00:04:05.981( 245981.117 ms.)| 14.93 | 5| 1484454471| 4| .00001|00:00:39.144( 39144.221 ms.)| 2.38 | 6| 2194493487| 4| .00001|00:00:18.182( 18182.816 ms.)| 1.10 | 7| 1053044345| 1 | .00000|00:00:16.611( 16611.722 ms.)| 1.01 | 8| 3644780286| 1 | .00000|00:00:00.436( 436.205 ms.)| .03

TOP10 SQL kanthi maksimal wektu eksekusi

Panjaluk

SELECT 
  id AS snapshotid , 
  queryid , 
  snapshot_timestamp ,  
  max_time 
FROM 
  pg_stat_history 
WHERE 
  queryid IS NOT NULL AND 
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
ORDER BY 4 DESC 
LIMIT 10

--------------------------------------------------- ---------------------------------------------------- | TOP10 SQL BY MAX EXECUTION TIME | #| snapshot | snapshotID| pitakon | max_time (ms) +----------------------------------- ------------------------------------------- | 1 | 05.04.2019/01/03 4169:655729273| 00| 02| 01.869:121869.981:2( 04.04.2019 ms.) | 17| 00/4153/821760255 00:01| 41.570| 101570.841| 3:04.04.2019:16( 00 ms.) | 4146| 821760255/00/01 41.570:101570.841| 4| 04.04.2019| 16:00:4144( 4152624390 ms.) | 00| 01/36.964/96964.607 5:04.04.2019| 17| 00| 4151:4152624390:00(01 ms.) | 36.964| 96964.607/6/05.04.2019 10:00| 4188| 1484454471| 00:01:33.452(93452.150 ms.) | 7| 04.04.2019/17/00 4150:2460318461| 00| 01| 33.113:93113.835:8( 04.04.2019 ms.) | 15| 00/4140/1484454471 00:00| 11.892| 11892.302| 9:04.04.2019:16 (00 ms.) | 4145| 1484454471/00/00 11.892:11892.302| 10| 04.04.2019| 17:00:4152( 1484454471 ms.) | 00| 00/11.892/11892.302 XNUMX:XNUMX| XNUMX| XNUMX| XNUMX:XNUMX:XNUMX( XNUMX ms.) | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX:XNUMX:XNUMX(XNUMX ms.)

TOP10 SQL dening SHARED buffer maca / nulis

Panjaluk

SELECT 
  id AS snapshotid , 
  queryid ,
  snapshot_timestamp , 
  shared_blks_read , 
  shared_blks_written 
FROM 
  pg_stat_history
WHERE 
  queryid IS NOT NULL AND 
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT AND
  ( shared_blks_read > 0 OR shared_blks_written > 0 )
ORDER BY 4 DESC  , 5 DESC 
LIMIT 10

--------------------------------------------------- ------------------------------------ | TOP10 SQL BY SHARED buffer maca / nulis | #| snapshot | snapshotID| pitakon | pamblokiran bareng diwaca| tulis blok bareng +----+-------------------+---------- --------------------------------------- | 1 | 04.04.2019/17/00 4153:821760255| 797308| 0| 2| 04.04.2019 | 16| 00/4146/821760255 797308:0| 3| 05.04.2019| 01| 03 | 4169| 655729273/797158/0 4:04.04.2019| 16| 00| 4144| 4152624390 | 756514| 0/5/04.04.2019 17:00| 4151| 4152624390| 756514| 0 | 6| 04.04.2019/17/00 4150:2460318461| 734117| 0| 7| 04.04.2019 | 17| 00/4155/3644780286 52973:0| 8| 05.04.2019| 01| 03 | 4168| 1053044345/52818/0 9:04.04.2019| 15| 00| 4141| 2194493487 | 52813| 0/10/04.04.2019 16:00| 4147| 2194493487| 52813| 0 | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX| XNUMX | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX| XNUMX ------------------------------------------------- -------------------------------------------------

Histogram distribusi pitakon kanthi wektu eksekusi maksimal

Njaluk

SELECT  
  MIN(max_time) AS hist_min  , 
  MAX(max_time) AS hist_max , 
  (( MAX(max_time) - MIN(min_time) ) / hist_columns ) as hist_width
FROM 
  pg_stat_history 
WHERE 
  queryid IS NOT NULL AND
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT ;

SELECT 
  SUM(calls) AS calls
FROM 
  pg_stat_history 
WHERE 
  queryid IS NOT NULL AND
  database_id =DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT AND 
  ( max_time >= hist_current_min AND  max_time < hist_current_max ) ;

|------------------------------------------------ ---------------------------------------------------- | MAX_TIME HISTOGRAM | TOTAL TELPON : 33851920 | MIN WAKTU : 00:00:01.063 | WAKTU MAKSIMAL : 00:02:01.869 ------------------------------------ -------- ---------------------------- | durasi min | wektu maksimal| telpon +---------------------------------+------------ ---------------------+---------- | 00:00:01.063( 1063.830 ms.) | 00:00:13.144( 13144.445 ms.) | 9 | 00:00:13.144( 13144.445 ms.) | 00:00:25.225( 25225.060 ms.) | 0 | 00:00:25.225( 25225.060 ms.) | 00:00:37.305( 37305.675 ms.) | 0 | 00:00:37.305( 37305.675 ms.) | 00:00:49.386( 49386.290 ms.) | 0 | 00:00:49.386( 49386.290 ms.) | 00:01:01.466( 61466.906 ms.) | 0 | 00:01:01.466( 61466.906 ms.) | 00:01:13.547( 73547.521 ms.) | 0 | 00:01:13.547( 73547.521 ms.) | 00:01:25.628( 85628.136 ms.) | 0 | 00:01:25.628( 85628.136 ms.) | 00:01:37.708( 97708.751 ms.) | 4 | 00:01:37.708( 97708.751 ms.) | 00:01:49.789( 109789.366 ms.) | 2 | 00:01:49.789( 109789.366 ms.) | 00:02:01.869( 121869.981 ms.) | 0

TOP10 Snapshots dening Query per Detik

Njaluk

--pg_qps.sql
--Calculate Query Per Second 
CREATE OR REPLACE FUNCTION pg_qps( pg_stat_history_id integer ) RETURNS double precision AS $$
DECLARE
 pg_stat_history_rec record ;
 prev_pg_stat_history_id integer ;
 prev_pg_stat_history_rec record;
 total_seconds double precision ;
 result double precision;
BEGIN 
  result = 0 ;
  
  SELECT *
  INTO pg_stat_history_rec
  FROM 
    pg_stat_history
  WHERE id = pg_stat_history_id ;

  IF pg_stat_history_rec.snapshot_timestamp IS NULL 
  THEN
    RAISE EXCEPTION 'ERROR - Not found pg_stat_history for id = %',pg_stat_history_id;
  END IF ;  
  
 --RAISE NOTICE 'pg_stat_history_id = % , snapshot_timestamp = %', pg_stat_history_id , 
 pg_stat_history_rec.snapshot_timestamp ;
  
  SELECT 
    MAX(id)   
  INTO
    prev_pg_stat_history_id
  FROM
    pg_stat_history
  WHERE 
    database_id = pg_stat_history_rec.database_id AND
	queryid IS NULL AND
	id < pg_stat_history_rec.id ;

  IF prev_pg_stat_history_id IS NULL 
  THEN
    RAISE NOTICE 'Not found previous pg_stat_history shapshot for id = %',pg_stat_history_id;
	RETURN NULL ;
  END IF;
  
  SELECT *
  INTO prev_pg_stat_history_rec
  FROM 
    pg_stat_history
  WHERE id = prev_pg_stat_history_id ;
  
  --RAISE NOTICE 'prev_pg_stat_history_id = % , prev_snapshot_timestamp = %', prev_pg_stat_history_id , prev_pg_stat_history_rec.snapshot_timestamp ;    

  total_seconds = extract(epoch from ( pg_stat_history_rec.snapshot_timestamp - prev_pg_stat_history_rec.snapshot_timestamp ));
  
  --RAISE NOTICE 'total_seconds = % ', total_seconds ;    
  
  --RAISE NOTICE 'calls = % ', pg_stat_history_rec.calls ;      
  
  IF total_seconds > 0 
  THEN
    result = pg_stat_history_rec.calls / total_seconds ;
  ELSE
   result = 0 ; 
  END IF;
   
 RETURN result ;
END
$$ LANGUAGE plpgsql;


SELECT 
  id , 
  snapshot_timestamp ,
  calls , 	
  total_time , 
  ( select pg_qps( id )) AS QPS ,
  blk_read_time ,
  blk_write_time
FROM 
  pg_stat_history
WHERE 
  queryid IS NULL AND 
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT AND
  ( select pg_qps( id )) IS NOT NULL 
ORDER BY 5 DESC 
LIMIT 10

|------------------------------------------------ ---------------------------------------------------- | TOP10 Snapshots dipesen dening nomer QueryPerSeconds -------------------------------------- ------ ------------------------------------------- ------ ------------------------------------------- | #| snapshot | snapshotID| nimbali | total dbtime| QPS | Wektu I/O | I/O wektu % +------+--------------------------------- ----+----------+--------- ---------------------------------------------------- | 1 | 04.04.2019/20/04 4161:5758631| 00| 06| 30.513:390513.926:1573.396( 00 ms.)| 00| 01.470:1470.110:376( 2 ms.)| .04.04.2019 | 17| 00/4149/3529197 00:11| 48.830| 708830.618| 980.332:00:12( 47.834 ms.)| 767834.052| 108.324:3:04.04.2019( 16 ms.)| 00 | 4143| 3525360/00/10 13.492:613492.351| 979.267| 00| 08:41.396:521396.555( 84.988 ms.)| 4| 04.04.2019:21:03( 4163 ms.)| 2781536 | 00| 03/06.470/186470.979 785.745:00| 00| 00.249| 249.865:134:5( 04.04.2019 ms.)| 19| 03:4159:2890362( 00 ms.)| .03 | 16.784| 196784.755/776.979/00 00:01.441| 1441.386| 732| 6:04.04.2019:14( 00 ms.)| 4137| 2397326:00:04( 43.033 ms.)| .283033.854 | 665.924| 00/00/00.024 24.505:009 | 7| 04.04.2019| 15:00:4139( 2394416 ms.)| 00| 04:51.435:291435.010( 665.116 ms.)| .00 | 00| 12.025/12025.895/4.126 8:04.04.2019| 13| 00| 4135:2373043:00( 04 ms.)| 26.791| 266791.988:659.179:00( 00 ms.)| 00.064 | 64.261| 024/9/05.04.2019 01:03 | 4167| 4387191| 00:06:51.380( 411380.293 ms.)| 609.332| 00:05:18.847( 318847.407 ms.)| .77.507 | 10| 04.04.2019/18/01 4157:1145596| 00| 01| 19.217:79217.372:313.004( 00 ms.)| 00| 01.319:1319.676:1.666( XNUMX ms.)| XNUMX | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX:XNUMX:XNUMX( XNUMX ms.)| XNUMX| XNUMX:XNUMX:XNUMX( XNUMX ms.)| XNUMX

Riwayat Eksekusi Saben Jam karo QueryPerSeconds lan Wektu I/O

Panjaluk

SELECT 
  id , 
  snapshot_timestamp ,
  calls , 	
  total_time , 
  ( select pg_qps( id )) AS QPS ,
  blk_read_time ,
  blk_write_time
FROM 
  pg_stat_history
WHERE 
  queryid IS NULL AND 
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
ORDER BY 2

|-----------------------------------------------------------------------------------------------
| HOURLY EXECUTION HISTORY  WITH QueryPerSeconds and I/O Time
-----------------------------------------------------------------------------------------------------------------------------------------------
| QUERY PER SECOND HISTORY
|    #|          snapshot| snapshotID|      calls|                      total dbtime|        QPS|                          I/O time| I/O time %
+-----+------------------+-----------+-----------+----------------------------------+-----------+----------------------------------+-----------
|    1|  04.04.2019 11:00|       4131|       3747|  00:00:00.835(       835.374 ms.)|      1.041|  00:00:00.000(          .000 ms.)|       .000
|    2|  04.04.2019 12:00|       4133|    1002722|  00:01:52.419(    112419.376 ms.)|    278.534|  00:00:00.149(       149.105 ms.)|       .133
|    3|  04.04.2019 13:00|       4135|    2373043|  00:04:26.791(    266791.988 ms.)|    659.179|  00:00:00.064(        64.261 ms.)|       .024
|    4|  04.04.2019 14:00|       4137|    2397326|  00:04:43.033(    283033.854 ms.)|    665.924|  00:00:00.024(        24.505 ms.)|       .009
|    5|  04.04.2019 15:00|       4139|    2394416|  00:04:51.435(    291435.010 ms.)|    665.116|  00:00:12.025(     12025.895 ms.)|      4.126
|    6|  04.04.2019 16:00|       4143|    3525360|  00:10:13.492(    613492.351 ms.)|    979.267|  00:08:41.396(    521396.555 ms.)|     84.988
|    7|  04.04.2019 17:00|       4149|    3529197|  00:11:48.830(    708830.618 ms.)|    980.332|  00:12:47.834(    767834.052 ms.)|    108.324
|    8|  04.04.2019 18:01|       4157|    1145596|  00:01:19.217(     79217.372 ms.)|    313.004|  00:00:01.319(      1319.676 ms.)|      1.666
|    9|  04.04.2019 19:03|       4159|    2890362|  00:03:16.784(    196784.755 ms.)|    776.979|  00:00:01.441(      1441.386 ms.)|       .732
|   10|  04.04.2019 20:04|       4161|    5758631|  00:06:30.513(    390513.926 ms.)|   1573.396|  00:00:01.470(      1470.110 ms.)|       .376
|   11|  04.04.2019 21:03|       4163|    2781536|  00:03:06.470(    186470.979 ms.)|    785.745|  00:00:00.249(       249.865 ms.)|       .134
|   12|  04.04.2019 23:03|       4165|    1443155|  00:01:34.467(     94467.539 ms.)|    200.438|  00:00:00.015(        15.287 ms.)|       .016
|   13|  05.04.2019 01:03|       4167|    4387191|  00:06:51.380(    411380.293 ms.)|    609.332|  00:05:18.847(    318847.407 ms.)|     77.507
|   14|  05.04.2019 02:03|       4171|     189852|  00:00:10.989(     10989.899 ms.)|     52.737|  00:00:00.539(       539.110 ms.)|      4.906
|   15|  05.04.2019 03:01|       4173|       3627|  00:00:00.103(       103.000 ms.)|      1.042|  00:00:00.004(         4.131 ms.)|      4.010
|   16|  05.04.2019 04:00|       4175|       3627|  00:00:00.085(        85.235 ms.)|      1.025|  00:00:00.003(         3.811 ms.)|      4.471
|   17|  05.04.2019 05:00|       4177|       3747|  00:00:00.849(       849.454 ms.)|      1.041|  00:00:00.006(         6.124 ms.)|       .721
|   18|  05.04.2019 06:00|       4179|       3747|  00:00:00.849(       849.561 ms.)|      1.041|  00:00:00.000(          .051 ms.)|       .006
|   19|  05.04.2019 07:00|       4181|       3747|  00:00:00.839(       839.416 ms.)|      1.041|  00:00:00.000(          .062 ms.)|       .007
|   20|  05.04.2019 08:00|       4183|       3747|  00:00:00.846(       846.382 ms.)|      1.041|  00:00:00.000(          .007 ms.)|       .001
|   21|  05.04.2019 09:00|       4185|       3747|  00:00:00.855(       855.426 ms.)|      1.041|  00:00:00.000(          .065 ms.)|       .008
|   22|  05.04.2019 10:00|       4187|       3797|  00:01:40.150(    100150.165 ms.)|      1.055|  00:00:21.845(     21845.217 ms.)|     21.812

Teks kabeh SQL milih

Panjaluk

SELECT 
  queryid , 
  query 
FROM 
  pg_stat_history
WHERE 
  queryid IS NOT NULL AND 
  database_id = DATABASE_ID  AND
  snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY queryid , query

Asile

Kaya sing sampeyan ngerteni, kanthi cara sing cukup prasaja, sampeyan bisa entuk akeh informasi migunani babagan beban kerja lan kahanan database.

Cathetan:Yen sampeyan ndandani queryid ing pitakon, mula kita bakal entuk riwayat kanggo panyuwunan sing kapisah (supaya ngirit papan, laporan kanggo panyuwunan sing kapisah diilangi).

Dadi, data statistik babagan kinerja query kasedhiya lan diklumpukake.
Tahap pisanan "pengumpulan data statistik" wis rampung.

Sampeyan bisa nerusake menyang tahap kapindho - "konfigurasi metrik kinerja".


Nanging iki crita sing beda.

Terus ...

Source: www.habr.com