From 21adedebe5cc7a2b4e7bb944e9eebaebd53e21cb Mon Sep 17 00:00:00 2001 From: Andreas Motl Date: Fri, 11 Apr 2025 17:46:54 +0200 Subject: [PATCH] Naming things: Use "Optimization and scaling", not "productizing" --- docs/performance/index.rst | 2 +- docs/performance/{designing_for_scale.rst => scaling.rst} | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) rename docs/performance/{designing_for_scale.rst => scaling.rst} (96%) diff --git a/docs/performance/index.rst b/docs/performance/index.rst index a3cccc9f..e29673fa 100644 --- a/docs/performance/index.rst +++ b/docs/performance/index.rst @@ -16,5 +16,5 @@ performance tuning and sharding. inserts/index selects optimization - designing_for_scale + scaling storage diff --git a/docs/performance/designing_for_scale.rst b/docs/performance/scaling.rst similarity index 96% rename from docs/performance/designing_for_scale.rst rename to docs/performance/scaling.rst index d969d66d..d7b3b2a2 100644 --- a/docs/performance/designing_for_scale.rst +++ b/docs/performance/scaling.rst @@ -1,8 +1,8 @@ -.. _topics-to-watch-out-when-productizing-cratedb: +.. _performance-scaling: -####################################### - Key design considerations for scaling -####################################### +################## + Design for scale +################## This article explores critical design considerations to successfully scale CrateDB in large production environments to ensure performance and reliability