PG中需要給共享內(nèi)存分配多少內(nèi)存?為什么?
綜合指南:postgresql shared buffers
本文主要針對下面問題詳述PG的共享內(nèi)存:PG中需要給共享內(nèi)存分配多少內(nèi)存?為什么?
非常奇怪,為什么我的RDS PG需要使用系統(tǒng)RAM的25%,而Aurora的PG卻需要分配75%?
理解PG中的共享內(nèi)存及操作系統(tǒng)的緩存
首先提出個問題:PG中的bgwriter進(jìn)程是干什么的?
如果回答是將臟頁刷到磁盤的,那這就錯了。他僅僅將臟頁刷寫到操作系統(tǒng)的緩存,然后由操作系統(tǒng)調(diào)用sync將操作系統(tǒng)緩存刷寫到磁盤。有點(diǎn)迷惑?那么接著我們說道說道。
由于PG輕量的特性,他高度依賴操作系統(tǒng)緩存,通過操作系統(tǒng)感知文件系統(tǒng)、磁盤布局以及讀寫數(shù)據(jù)文件。下圖幫助了解數(shù)據(jù)如何在磁盤和共享緩存之間流動。
因此當(dāng)發(fā)起“select *from emp”時,數(shù)據(jù)會加載到操作系統(tǒng)緩存然后才到shared buffer。同樣當(dāng)將臟頁向磁盤刷寫時,也是先到操作系統(tǒng)緩存,然后由操作系統(tǒng)調(diào)用fsync()將操作系統(tǒng)緩存中數(shù)據(jù)持久化到磁盤。這樣PG實(shí)際上由兩份數(shù)據(jù),看起來有些浪費(fèi)空間,但是操作系統(tǒng)緩存是一個簡單的LRU而不是數(shù)據(jù)庫優(yōu)化的clock sweep algorithm。一旦在shared_buffers中命中,那么讀就不會下沉到操作系統(tǒng)緩存。如果shared buffer和操作系統(tǒng)緩存有相同頁,操作系統(tǒng)緩存中的頁很快會被驅(qū)逐替換。
我能影響操作系統(tǒng)的fsync將臟頁刷回磁盤嗎?
當(dāng)然,通過postgresql.conf中參數(shù)bgwriter_flush_after,該參數(shù)整型,默認(rèn)512KB。當(dāng)后臺寫進(jìn)程寫了這么多數(shù)據(jù)時,會強(qiáng)制OS發(fā)起sync將cache中數(shù)據(jù)刷到底層存儲。這樣會限制內(nèi)核頁緩存中的臟數(shù)據(jù)數(shù)量,從而減小checkpoint時間或者后臺大批量寫回數(shù)據(jù)的時間。
不僅僅時bgwriter,即使checkpoint進(jìn)程和用戶進(jìn)程也從shared buffer刷寫臟頁到OS cache?梢酝ㄟ^checkpoint_flush_after影響checkpoint進(jìn)程的fsync,通過backend_flush_after影響后臺進(jìn)程的fsync。
如果給OS cache很小值會怎么樣?
正如上文所述,一旦頁被標(biāo)記為臟,他就會刷寫到操作系統(tǒng)緩存。操作系統(tǒng)可以更加自由地根據(jù)傳入的流量進(jìn)行IO調(diào)度。如果OS cache太小,則無法重新對write進(jìn)行排序從而優(yōu)化IO。這對于寫操作頻繁的工作負(fù)載尤為重要,所以操作系統(tǒng)緩存大學(xué)也很重要。
如果給shared buffer很小值會怎么樣?
數(shù)據(jù)庫操作都在shared buffer,所以最好為shared buffer分配足夠空間。
建議值多大?
PG推薦系統(tǒng)內(nèi)存的25%給shared buffer,當(dāng)然可以根據(jù)環(huán)境進(jìn)行調(diào)整。
如果查看shared buffer中內(nèi)容?
PG的buffer cache擴(kuò)展可以幫助實(shí)時查看shared buffer中內(nèi)容。從shared_buffers中采集信息保存到pg_buffercache表中:
create extension pg_buffercache;
安裝好后,執(zhí)行下面查詢查看內(nèi)容:
SELECT c.relname
, pg_size_pretty(count(*) * 8192) as buffered
, round(100.0 * count(*) / ( SELECT setting FROM pg_settings WHERE name='shared_buffers')::integer,1) AS buffers_percent
, round(100.0 * count(*) * 8192 / pg_relation_size(c.oid),1) AS percent_of_relation
FROM pg_class c
INNER JOIN pg_buffercache b ON b.relfilenode = c.relfilenode
INNER JOIN pg_database d ON (b.reldatabase = d.oid AND d.datname = current_database())
WHERE pg_relation_size(c.oid) > 0
GROUP BY c.oid, c.relname
ORDER BY 3 DESC
LIMIT 10;
輸出:
postgres=# SELECT c.relname postgres-# , pg_size_pretty(count(*) * 8192) as buffered postgres-# , round(100.0 * count(*) / ( SELECT setting FROM pg_settings WHERE name='shared_buffers')::integer,1) AS buffers_percent postgres-# , round(100.0 * count(*) * 8192 / pg_relation_size(c.oid),1) AS percent_of_relation postgres-# FROM pg_class c postgres-# INNER JOIN pg_buffercache b ON b.relfilenode = c.relfilenode postgres-# INNER JOIN pg_database d ON (b.reldatabase = d.oid AND d.datname = current_database()) postgres-# WHERE pg_relation_size(c.oid) > 0 postgres-# GROUP BY c.oid, c.relname postgres-# ORDER BY 3 DESC postgres-# LIMIT 10; relname | buffered | buffers_percent | percent_of_relation ---------------------------+------------+-----------------+--------------------- pg_operator | 80 kB | 0.1 | 71.4 pg_depend_reference_index | 96 kB | 0.1 | 27.9 pg_am | 8192 bytes | 0.0 | 100.0 pg_amproc | 24 kB | 0.0 | 100.0 pg_cast | 8192 bytes | 0.0 | 50.0 pg_depend | 64 kB | 0.0 | 14.0 pg_index | 32 kB | 0.0 | 100.0 pg_description | 40 kB | 0.0 | 14.3 pg_language | 8192 bytes | 0.0 | 100.0 pg_amop | 40 kB | 0.0 | 83.3 (10 rows)
如何感知數(shù)據(jù)到達(dá)操作系統(tǒng)緩存層?
需要安裝包pgfincore:
As root user: export PATH=/usr/local/pgsql/bin:$PATH //Set the path to point pg_config. tar -xvf pgfincore-v1.1.1.tar.gz cd pgfincore-1.1.1 make clean make make install Now connect to PG and run below command postgres=# CREATE EXTENSION pgfincore;
執(zhí)行下面命令:
select c.relname,pg_size_pretty(count(*) * 8192) as pg_buffered,
round(100.0 * count(*) /
(select setting
from pg_settings
where name='shared_buffers')::integer,1)
as pgbuffer_percent,
round(100.0*count(*)*8192 / pg_table_size(c.oid),1) as percent_of_relation,
( select round( sum(pages_mem) * 4 /1024,0 )
from pgfincore(c.relname::text) )
as os_cache_M(jìn)B ,
round(100 * (
select sum(pages_mem)*4096
from pgfincore(c.relname::text) )/ pg_table_size(c.oid),1)
as os_cache_percent_of_relation,
pg_size_pretty(pg_table_size(c.oid)) as rel_size
from pg_class c
inner join pg_buffercache b on b.relfilenode=c.relfilenode
inner join pg_database d on (b.reldatabase=d.oid and d.datname=current_database()
and c.relnamespace=(select oid from pg_namespace where nspname='public'))
group by c.oid,c.relname
order by 3 desc limit 30;
輸出:
relname |pg_buffered|pgbuffer_per|per_of_relation|os_cache_mb|os_cache_per_of_relation|rel_size
---------+-----------+------------+---------------+-----------+------------------------+--------
emp | 4091 MB | 99.9 | 49.3 | 7643 | 92.1 | 8301 MB
pg_buffered表示PG buffer cache中有多少數(shù)據(jù),pgbuffer_percent表示pg_buffered/total_buffer_size*100。os_cache_mb表示OS cache中緩存多少。我們的表emp有8301MB數(shù)據(jù),92%數(shù)據(jù)在OS cache,49.3%在shared buffers,大約50%的數(shù)據(jù)是冗余的。
為什么Aurora PG推薦75%的內(nèi)存給shared buffer?
Aurora不使用文件系統(tǒng)緩存,因此可以提升shared_buffers大小以提升性能。最佳實(shí)踐值為75%。Work_mem、maintenance_work_mem和其他本地內(nèi)存不是shared buffer的一部分。如果應(yīng)用請求大量客戶端連接,或需要大量work_mem時,需要將這個值調(diào)小。

請輸入評論內(nèi)容...
請輸入評論/評論長度6~500個字
最新活動更多
推薦專題
-
10 月之暗面,絕地反擊
- 1 UALink規(guī)范發(fā)布:挑戰(zhàn)英偉達(dá)AI統(tǒng)治的開始
- 2 北電數(shù)智主辦酒仙橋論壇,探索AI產(chǎn)業(yè)發(fā)展新路徑
- 3 降薪、加班、裁員三重暴擊,“AI四小龍”已折戟兩家
- 4 “AI寒武紀(jì)”爆發(fā)至今,五類新物種登上歷史舞臺
- 5 國產(chǎn)智駕迎戰(zhàn)特斯拉FSD,AI含量差幾何?
- 6 光計算迎來商業(yè)化突破,但落地仍需時間
- 7 東陽光:2024年扭虧、一季度凈利大增,液冷疊加具身智能打開成長空間
- 8 地平線自動駕駛方案解讀
- 9 封殺AI“照騙”,“淘寶們”終于不忍了?
- 10 優(yōu)必選:營收大增主靠小件,虧損繼續(xù)又逢關(guān)稅,能否乘機(jī)器人東風(fēng)翻身?