From f98cf46fff5481d82ffe95b1d366e659a9a6dd32 Mon Sep 17 00:00:00 2001 From: ArthurFlageul Date: Wed, 20 Dec 2023 11:07:28 +0100 Subject: [PATCH] fix markup --- .../concepts/mysql-tuning-and-concurrency.rst | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/products/mysql/concepts/mysql-tuning-and-concurrency.rst b/docs/products/mysql/concepts/mysql-tuning-and-concurrency.rst index 03a9b5b4a4..d1ab89f1d4 100644 --- a/docs/products/mysql/concepts/mysql-tuning-and-concurrency.rst +++ b/docs/products/mysql/concepts/mysql-tuning-and-concurrency.rst @@ -12,8 +12,8 @@ There are several key calculations which are fundamental to tuning: - Thread buffers - Concurrency -.. topic:: - **Query output is for reference only** +.. important:: + Query output is for reference only. Queries should be run per service for accuracy and re-evaluated periodically for change. @@ -83,9 +83,10 @@ Queries may use part or all of the allocation. | 17.9375 | +-------------------+ -.. topic:: - **The actual amount of memory a query could use is technically unbounded.** +.. important:: + The actual amount of memory a query could use is technically unbounded. + Uncontrolled memory allocations and temporary table usage can adversely affect memory allocation. The data dictionary size is based on the number of tables, fields and indexes within the database. @@ -106,8 +107,9 @@ The :doc:`max_connections ` parameter is based off th | 226 | +-------------------+ -.. topic:: - **This parameter should be used as a guideline only**. +.. important:: + + This parameter should be used as a guideline only. By default, ``max_connections`` is configured for *optimistic* concurrency using all available memory.