学习opengauss-内存分配

学习opengauss内存分配

opengauss使用线程管理

ps -ef|grep gaussdb
ps -Tp pid
[og@opengauss ~]$ ps -ef|grep gauss
og         13752       1  2 12:40 ?        00:00:06 /opt/opengauss/openGauss-server/mppdb_temp_install/bin/gaussdb
og         13956    8654  0 12:44 pts/0    00:00:00 grep --color=auto gauss
[og@opengauss ~]$ ps -Tp 13752
    PID    SPID TTY          TIME CMD
  13752   13752 ?        00:00:00 gaussdb
  13752   13753 ?        00:00:00 jemalloc_bg_thd
  13752   13758 ?        00:00:00 gaussdb
  13752   13759 ?        00:00:00 syslogger
  13752   13760 ?        00:00:00 alarm
  13752   13761 ?        00:00:00 reaper
  13752   13785 ?        00:00:00 gaussdb
  13752   13786 ?        00:00:00 gaussdb
  13752   13787 ?        00:00:00 gaussdb
  13752   13789 ?        00:00:00 checkpointer
  13752   13790 ?        00:00:00 Spbgwriter
  13752   13791 ?        00:00:00 pagewriter
  13752   13792 ?        00:00:03 pagewriter
  13752   13793 ?        00:00:00 pagewriter
  13752   13794 ?        00:00:00 pagewriter
  13752   13795 ?        00:00:00 pagewriter
  13752   13796 ?        00:00:00 WALwriter
  13752   13797 ?        00:00:00 WALwriteraux
  13752   13798 ?        00:00:00 AVClauncher
  13752   13799 ?        00:00:00 Jobscheduler
  13752   13800 ?        00:00:00 asyncundolaunch
  13752   13801 ?        00:00:00 globalstats
  13752   13802 ?        00:00:00 applylauncher
  13752   13803 ?        00:00:00 statscollector
  13752   13804 ?        00:00:00 txnsnapcapturer
  13752   13805 ?        00:00:00 CfsShrinker
  13752   13806 ?        00:00:01 percentworker
  13752   13807 ?        00:00:03 ashworker
  13752   13808 ?        00:00:01 TrackStmtWorker
  13752   13809 ?        00:00:00 auditor
  13752   13810 ?        00:00:00 2pccleaner
  13752   13811 ?        00:00:00 faultmonitor
  13752   13812 ?        00:00:00 WLMworker
  13752   13813 ?        00:00:00 WLMmonitor
  13752   13814 ?        00:00:00 WLMarbiter
  13752   13815 ?        00:00:00 undorecycler
[og@opengauss ~]$

opengauss使用共享内存段

ipcs -m

查看buffer设置

[og@opengauss ogdata]$ grep -v ^#  postgresql.conf |grep buffers
shared_buffers = 128MB                  # min 128kB
bulk_write_ring_size = 2GB              # for bulkload, max shared_buffers
cstore_buffers = 32MB         #min 16MB


[og@opengauss ogdata]$ ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x0052e2c1 0          og         600        577661256  1

[og@opengauss ogdata]$ echo 577661256/1024/1024 | bc
550

550MB - 128MB - 32MB = 390MB


修改buffers ,查看ipcs -m

#############change shared_buffers to 512MB

grep -v ^#  postgresql.conf |grep buffers
shared_buffers = 512MB                  # min 128kB
bulk_write_ring_size = 2GB              # for bulkload, max shared_buffers
cstore_buffers = 32MB         #min 16MB

[og@opengauss ~]$ env|grep PGDATA
PGDATA=/opt/opengauss/ogdata

[og@opengauss ~]$ gs_ctl stop
[2024-05-06 12:37:13.745][13420][][gs_ctl]: gs_ctl stopped ,datadir is /opt/opengauss/ogdata
waiting for server to shut down..... done
server stopped
[og@opengauss ~]$ gs_ctl start
[2024-05-06 12:37:19.446][13436][][gs_ctl]: gs_ctl started,datadir is /opt/opengauss/ogdata
[2024-05-06 12:37:19.505][13436][][gs_ctl]: waiting for server to start...
.0 LOG:  [Alarm Module]can not read GAUSS_WARNING_TYPE env.


[og@opengauss ~]$ ipcs -m

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x0052e2c1 98304      og         600        1805535560 1

[og@opengauss ~]$ echo 1805535560/1024/1024 | bc
1721
[og@opengauss ~]$

[og@opengauss ~]$ echo 1721-512-32|bc
1177



疑问

这1177MB是分配给谁了?

参考

ipci.cpp, opengauss的代码

Size ComputeTotalSizeOfShmem()
{
        Size size;
        /*
         * Size of the openGauss shared-memory block is estimated via
         * moderately-accurate estimates for the big hogs, plus 100K for the
         * stuff that's too small to bother with estimating.
         *
         * We take some care during this phase to ensure that the total size
         * request doesn't overflow size_t.  If this gets through, we don't
         * need to be so careful during the actual allocation phase.
         */
        size = 100000;
        size = add_size(size, hash_estimate_size(SHMEM_INDEX_SIZE, sizeof(ShmemIndexEnt)));
        size = add_size(size, BufferShmemSize());
        size = add_size(size, ReplicationSlotsShmemSize());
#ifndef ENABLE_MULTIPLE_NODES
        size = add_size(size, ReplicationOriginShmemSize());
        size = add_size(size, ApplyLauncherShmemSize());
#endif
        size = add_size(size, LockShmemSize());
        size = add_size(size, PredicateLockShmemSize());
        size = add_size(size, ProcGlobalShmemSize());
        size = add_size(size, XLOGShmemSize());
        size = add_size(size, XLogStatShmemSize());
        size = add_size(size, CLOGShmemSize());
        size = add_size(size, CSNLOGShmemSize());
        size = add_size(size, mul_size(NUM_TWOPHASE_PARTITIONS, TwoPhaseShmemSize()));
        size = add_size(size, MultiXactShmemSize());
        size = add_size(size, LWLockShmemSize());
        size = add_size(size, ProcArrayShmemSize());
        size = add_size(size, RingBufferShmemSize());
        size = add_size(size, BackendStatusShmemSize());
        size = add_size(size, sessionTimeShmemSize());
        size = add_size(size, sessionStatShmemSize());
        size = add_size(size, sessionMemoryShmemSize());
        size = add_size(size, SInvalShmemSize());
        size = add_size(size, PMSignalShmemSize());
        size = add_size(size, ProcSignalShmemSize());
        size = add_size(size, CheckpointerShmemSize());
        size = add_size(size, PageWriterShmemSize());
        size = add_size(size, AutoVacuumShmemSize());
        size = add_size(size, WalSndShmemSize());
        size = add_size(size, WalRcvShmemSize());
        size = add_size(size, DataSndShmemSize());
        size = add_size(size, DataRcvShmemSize());
        /* DataSenderQueue, DataWriterQueue has the same size, WalDataWriterQueue is deleted */
        size = add_size(size, mul_size(2, DataQueueShmemSize()));
        size = add_size(size, CBMShmemSize());
        size = add_size(size, HaShmemSize());
        size = add_size(size, NotifySignalShmemSize());
        size = add_size(size, JobInfoShmemSize());
        size = add_size(size, BTreeShmemSize());
        size = add_size(size, SyncScanShmemSize());
        size = add_size(size, AsyncShmemSize());
        size = add_size(size, active_gtt_shared_hash_size());
        size = add_size(size, AsyncRollbackHashShmemSize());
        size = add_size(size, UndoWorkerShmemSize());
        size = add_size(size, TxnSnapCapShmemSize());
        size = add_size(size, RbCleanerShmemSize());

#ifdef PGXC
        size = add_size(size, NodeTablesShmemSize());
#endif

        size = add_size(size, TableSpaceUsageManager::ShmemSize());
        size = add_size(size, LsnXlogFlushChkShmemSize());
        size = add_size(size, heartbeat_shmem_size());
        size = add_size(size, MatviewShmemSize());
#ifndef ENABLE_MULTIPLE_NODES
        if(g_instance.attr.attr_storage.dcf_attr.enable_dcf) {
            size = add_size(size, DcfContextShmemSize());
        }
#endif
        size = add_size(size, CalShareStorageCtlSize());
        /* freeze the addin request size and include it */
        t_thrd.storage_cxt.addin_request_allowed = false;
        size = add_size(size, t_thrd.storage_cxt.total_addin_request);

        /* might as well round it off to a multiple of a typical page size */
        size = add_size(size, 8192 - (size % 8192));

        /* pca buffer size */
        size = add_size(size, pca_buffer_size());

        /* csf shrinker backend shared memory */
        size = add_size(size, CfsShrinkerShmemSize());

        if (g_instance.attr.attr_storage.dms_attr.enable_ondemand_recovery) {
            size = add_size(size, OndemandRecoveryShmemSize());
        }
        return size;
}


后续debug分析

通过nvim 做debug分析,记录每个函数调用后的size值,
在这里插入图片描述可以看出:
138行,139行增加最大. 分别是:

XLOGShmemSize, XlogStatShmemSize. 大概增加了128M.
为什么这2个函数增加这么多?
应该是postgresql 9.2的代码.

  • 6
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: OpenGauss-JDBC是一个Java数据库连接器,专门用于连接和操作OpenGauss数据库OpenGauss是一种高性能、高可靠性的关系型数据库管理系统,由华为公司开发,它具有良好的扩展性和容错性,在企业级应用中得到了广泛应用。 OpenGauss-JDBC的主要特点是速度快、安全性高、稳定性好和易于使用。它支持多种数据类型、运算符和函数,并且具有完整的事务管理功能和高级安全性特性。此外,OpenGauss-JDBC支持最新版的JDBC标准,可以与任何兼容JDBC的应用程序集成,包括Java Web应用程序、企业应用程序和数据分析应用程序。同时,OpenGauss-JDBC也提供了完整的SQL语法支持,可以访问OpenGauss数据库的所有数据和对象。 OpenGauss-JDBC还提供了一个良好的性能,使用Connection Pooling技术来缓存数据库连接,减少连接时间和开销。此外,它还支持批量操作和预编译语句、分布式事务和连接池调整等高级特性,使得开发人员可以轻松构建高性能的应用程序。 总之,OpenGauss-JDBC是一个非常强大的Java数据库连接器,它提供了丰富的功能和高性能,可以帮助企业轻松构建和管理OpenGauss数据库系统。 ### 回答2: opengauss-jdbc是一个Java数据库连接工具,它可以让Java程序能够与开源数据库opengauss进行交互和通讯。opengauss是面向企业级应用场景的高性能、高可靠、安全可信的开源数据库,同时支持传统SQL与融合分析与数据智能的全面能力。作为一个数据库连接工具,opengauss-jdbc支持多种连接方式和协议,如JDBC、ODBC、PgJDBC和libpq等,可以让Java程序员在编写数据应用程序时更加方便和高效地访问opengauss数据库opengauss-jdbc提供了大量的功能和API,如支持SQL语句的执行、批量操作、自定义数据类型、数据池管理、错误处理等。此外,opengauss-jdbc还提供了可自定义的参数和驱动程序设置,可以进行优化和提高系统性能。opengauss-jdbc还支持SSL协议等安全机制,可以保证安全性和数据完整性。 总之,opengauss-jdbc是一个强大的Java数据库连接工具,它使得Java程序员可以更加方便、高效和可靠地与opengauss数据库进行数据交互和管理。同时,它还为企业级应用提供了高性能、高可靠、安全可信的数据管理解决方案。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值