WIP 2
This commit is contained in:
parent
65ec82dd13
commit
f4b6828880
2 changed files with 9 additions and 1 deletions
|
@ -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)
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
+++
|
||||
title="Does Aerogramme use too much RAM?"
|
||||
title="Does Aerogramme use too much memory?"
|
||||
date=2024-02-15
|
||||
+++
|
||||
|
||||
|
|
Loading…
Reference in a new issue