From f4b6828880e58ff4a27c4ffceed2db011350b618 Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Thu, 22 Feb 2024 21:58:41 +0100 Subject: [PATCH] WIP 2 --- content/blog/2024-predictability-and-correctness/index.md | 8 ++++++++ content/blog/2024-ram-usage-encryption-s3/index.md | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/content/blog/2024-predictability-and-correctness/index.md b/content/blog/2024-predictability-and-correctness/index.md index b8a7392..fc1e3dd 100644 --- a/content/blog/2024-predictability-and-correctness/index.md +++ b/content/blog/2024-predictability-and-correctness/index.md @@ -14,6 +14,14 @@ In the following, I describe both aspect in details. ## More predictable performances +In the previous blog post, we asked ourselves [Does Aerogramme use too much memory?](@/blog/2024-ram-usage-encryption-s3/index.md). +From the discussion, we surfaced it was not acceptable that some specific queries (FETCH FULL or SEARCH TEXT) where loading the +full mailbox in memory. It's concerning as the mail server will be used by multiple users and as a limited amount of resources, +so we don't want a user allocating all the memory. In other words, we want to have a per-user resource usage that remain as stable as possible. +These ideas are developed more in depth in the Amazon article [Reliability & Constant Work](https://aws.amazon.com/fr/builders-library/reliability-and-constant-work/). + + + ![Fetch resource usage for Aerograme 0.2.1 & 0.2.2](fetch-full.png) ![Search resource usage for Aerograme 0.2.1 & 0.2.2](search-full.png) diff --git a/content/blog/2024-ram-usage-encryption-s3/index.md b/content/blog/2024-ram-usage-encryption-s3/index.md index d5b983c..8900914 100644 --- a/content/blog/2024-ram-usage-encryption-s3/index.md +++ b/content/blog/2024-ram-usage-encryption-s3/index.md @@ -1,5 +1,5 @@ +++ -title="Does Aerogramme use too much RAM?" +title="Does Aerogramme use too much memory?" date=2024-02-15 +++