MariaDB 沒有使用所有可用記憶體

我有一個包含大約 160.000 篇文章的 joomla 網站。我使用 10.4.6-MariaDB、nginx 和 php 7.3。

當我檢查我的伺服器時top，我看到 MariaDB 最多使用 3.3 MB 的記憶體，而我給了它 25GB，或者至少這是我的想法。

貝婁是我的摘錄50-server.cnf：

# If you use the same .cnf file for MariaDB of different versions,
# use this group for options that older servers don't understand
[mariadb-10.1]
innodb_log_buffer_size=2G
innodb_buffer_pool_size=25G
innodb_file_per_table= ON
sql_bin_log=0;

以上是在 Debian 8、nginx 上，託管 joomla 4 alpha 7 cms。

回應里克詹姆斯的評論：

需要很長時間的查詢是 7 秒：

SELECT DISTINCT a.id, a.title, a.alias, a.checked_out, a.checked_out_time, a.catid, a.state, a.access, a.created, a.created_by, a.created_by_alias, a.modified, a.ordering, a.featured, a.language, a.hits, a.publish_up, a.publish_down, a.introtext,l.title AS language_title, l.image AS language_image,uc.name AS editor,ag.title AS access_level,c.title AS category_title,ua.name AS author_name,`wa`.`stage_id` AS `stage_id`,`ws`.`title` AS `stage_title`,`ws`.`condition` AS `stage_condition`,`ws`.`workflow_id` AS `workflow_id`,COUNT(asso2.id)>1 as association
FROM bwn_content AS a
LEFT JOIN `bwn_languages` AS l ON l.lang_code = a.language
LEFT JOIN bwn_users AS uc ON uc.id=a.checked_out
LEFT JOIN bwn_viewlevels AS ag ON ag.id = a.access
LEFT JOIN bwn_categories AS c ON c.id = a.catid
LEFT JOIN bwn_users AS ua ON ua.id = a.created_by
INNER JOIN `bwn_workflow_associations` AS `wa` ON `wa`.`item_id` = `a`.`id`
INNER JOIN `bwn_workflow_stages` AS `ws` ON `ws`.`id` = `wa`.`stage_id`
LEFT JOIN bwn_associations AS asso ON asso.id = a.id AND asso.context='com_content.item'
LEFT JOIN bwn_associations AS asso2 ON asso2.key = asso.key
WHERE `ws`.`condition` IN (1, 0) AND `wa`.`extension`='com_content'
GROUP BY `a`.`id`,`a`.`title`,`a`.`alias`,`a`.`checked_out`,`a`.`checked_out_time`,`a`.`state`,`a`.`access`,`a`.`created`,`a`.`created_by`,`a`.`created_by_alias`,`a`.`modified`,`a`.`ordering`,`a`.`featured`,`a`.`language`,`a`.`hits`,`a`.`publish_up`,`a`.`publish_down`,`a`.`catid`,`l`.`title`,`l`.`image`,`uc`.`name`,`ag`.`title`,`c`.`title`,`ua`.`name`,`ws`.`title`,`ws`.`workflow_id`,`ws`.`condition`,`wa`.`stage_id`
ORDER BY a.id DESC

上述查詢的主表是

bwn_content 大約 1.5G，大約有 160.000 條記錄

上面的顯示創建語句是：

CREATE TABLE `bwn_content` (
 `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
 `asset_id` int(10) unsigned NOT NULL DEFAULT 0 COMMENT 'FK to the #__assets table.',
 `title` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
 `alias` varchar(400) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL DEFAULT '',
 `introtext` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
 `fulltext` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
 `state` tinyint(3) NOT NULL DEFAULT 0,
 `catid` int(10) unsigned NOT NULL DEFAULT 0,
 `created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
 `created_by` int(10) unsigned NOT NULL DEFAULT 0,
 `created_by_alias` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
 `modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
 `modified_by` int(10) unsigned NOT NULL DEFAULT 0,
 `checked_out` int(10) unsigned NOT NULL DEFAULT 0,
 `checked_out_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
 `publish_up` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
 `publish_down` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
 `images` text COLLATE utf8mb4_unicode_ci NOT NULL,
 `urls` text COLLATE utf8mb4_unicode_ci NOT NULL,
 `attribs` varchar(5120) COLLATE utf8mb4_unicode_ci NOT NULL,
 `version` int(10) unsigned NOT NULL DEFAULT 1,
 `ordering` int(11) NOT NULL DEFAULT 0,
 `metakey` text COLLATE utf8mb4_unicode_ci NOT NULL,
 `metadesc` text COLLATE utf8mb4_unicode_ci NOT NULL,
 `access` int(10) unsigned NOT NULL DEFAULT 0,
 `hits` int(10) unsigned NOT NULL DEFAULT 0,
 `metadata` text COLLATE utf8mb4_unicode_ci NOT NULL,
 `featured` tinyint(3) unsigned NOT NULL DEFAULT 0 COMMENT 'Set if article is featured.',
 `language` char(7) COLLATE utf8mb4_unicode_ci NOT NULL COMMENT 'The language code for the article.',
 `xreference` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' COMMENT 'A reference to enable linkages to external data sets.',
 PRIMARY KEY (`id`),
 KEY `idx_access` (`access`),
 KEY `idx_checkout` (`checked_out`),
 KEY `idx_state` (`state`),
 KEY `idx_catid` (`catid`),
 KEY `idx_createdby` (`created_by`),
 KEY `idx_featured_catid` (`featured`,`catid`),
 KEY `idx_language` (`language`),
 KEY `idx_xreference` (`xreference`),
 KEY `idx_alias` (`alias`(191))
) ENGINE=InnoDB AUTO_INCREMENT=165248 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_c

您的設置在一個[mariadb-10.1]部分中，因此 MariaDB 10.4 不會使用它。您需要將它們移動到例如 a[mariadb-10.4]或[mariadb]部分。

您可以使用以下命令從命令行客戶端檢查 MariaDB 使用的實際值：

SHOW VARIABLES LIKE 'innodb_log_buffer_size';
SHOW VARIABLES LIKE 'innodb_buffer_pool_size';

要查找數據 + 索引的大小，請執行以下查詢之一：

SELECT 
 round(sum(data_length + index_length) / 1024 / 1024, 1) "DB size (MB)"
FROM information_schema.tables;

這將顯示每個模式的大小 + 總數：

SELECT table_schema "DB name", 
 round(sum(data_length + index_length) / 1024 / 1024, 1) "DB size (MB)"
FROM information_schema.tables
GROUP BY table_schema WITH ROLLUP;

這將顯示特定數據庫中每個表的大小 + 總數：

SELECT table_name "table name",        
 round(sum(data_length + index_length) / 1024 / 1024, 1) "DB Size in MB"
FROM information_schema.tables
WHERE table_schema = 'joomla' 
GROUP BY table_name WITH ROLLUP;

引用自：https://dba.stackexchange.com/questions/242708