From 12f04a19b41255f7d3f1f4106288fcfcc8903523 Mon Sep 17 00:00:00 2001 From: naskya Date: Wed, 10 Apr 2024 14:45:25 +0900 Subject: [PATCH] docs (minor): update notice-for-admins.md --- docs/notice-for-admins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/notice-for-admins.md b/docs/notice-for-admins.md index ea952d776a..d831e38dd9 100644 --- a/docs/notice-for-admins.md +++ b/docs/notice-for-admins.md @@ -13,7 +13,7 @@ The time required to upgrade varies greatly depending on the database size and t - 70 seconds if the database stores 600,000 posts - 28 minutes if the database stores 12,000,000 posts -(i.e., it takes roughly (n * 0.23) minutes if there are (n * 100,000) posts) on a server with 2 GB of RAM. You may want to tweak your database configuration (`postgres.conf`) if the process is significantly slower than our experimental result. +(i.e., it takes roughly (𝑛 / 470,000) minutes where 𝑛 is the number of posts) on a server with 2 GB of RAM. You may want to tweak your database configuration (`postgres.conf`) if the process is significantly slower than our experimental result. The number of posts stored on your database can be found at `https://yourserver.example.com/admin/database` (or `notesCount` of `stats` API response).