summary refs log tree commit diff
path: root/develop/print.html
diff options
context:
space:
mode:
authorH-Shay <H-Shay@users.noreply.github.com>2021-12-01 03:05:49 +0000
committerH-Shay <H-Shay@users.noreply.github.com>2021-12-01 03:05:49 +0000
commitf863a7bbd835132e6023d2b09dc4f7ed2f8859d8 (patch)
tree404f0ddb3ed7ddd2daa9380333ea0c7870fc0f21 /develop/print.html
parentdeploy: e713855dca17a7605bae99ea8d71bc7f8657e4b8 (diff)
downloadsynapse-f863a7bbd835132e6023d2b09dc4f7ed2f8859d8.tar.xz
deploy: f1795463bf503a6fca909d77f598f641f9349f56
Diffstat (limited to 'develop/print.html')
-rw-r--r--develop/print.html3
1 files changed, 3 insertions, 0 deletions
diff --git a/develop/print.html b/develop/print.html
index 91df1d2f6d..e57c5138be 100644
--- a/develop/print.html
+++ b/develop/print.html
@@ -769,6 +769,9 @@ performance:</p>
 </ul>
 <p>Note that the appropriate values for those fields depend on the amount
 of free memory the database host has available.</p>
+<p>Additionally, admins of large deployments might want to consider using huge pages
+to help manage memory, especially when using large values of <code>shared_buffers</code>. You
+can read more about that <a href="https://www.postgresql.org/docs/10/kernel-resources.html#LINUX-HUGE-PAGES">here</a>.</p>
 <h2 id="porting-from-sqlite"><a class="header" href="#porting-from-sqlite">Porting from SQLite</a></h2>
 <h3 id="overview"><a class="header" href="#overview">Overview</a></h3>
 <p>The script <code>synapse_port_db</code> allows porting an existing synapse server