Deuxfleurs/aerogramme.deuxfleurs.fr
17
0
Fork 0
Code Pull requests Activity

fix markdown

Browse source
This commit is contained in:
Quentin 2024-02-18 11:20:57 +01:00
parent 718830a0b0
commit 4c836dbd10
Signed by: quentin
GPG key ID: E9602264D639FF68
1 changed files with 1 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
content/blog/2024-ram-usage-encryption-s3/index.md
View file

@ -408,10 +408,7 @@ For now, we want to start with 1 000 users, a 1k email INBOX, and a server of 8G
and Aerogramme seems ready for a first deployment in this context. Of course, in the long term, and Aerogramme seems ready for a first deployment in this context. Of course, in the long term,
we expect better ressource usages. we expect better ressource usages.
Based on this benchmark, I identify 3 low-hanging fruits to improve performances that do not require major design changes Based on this benchmark, I identify 3 low-hanging fruits to improve performances that do not require major design changes: 1) in FETCH+SEARCH queries, handling emails one after another instead of loading the full mailbox in memory, 2) streaming FETCH responses instead of aggregating them in memory, and 3) reducing the RAM usage of a base user by tweaking its Garage connectors configuration
: 1) in FETCH+SEARCH queries, handling emails one after another instead of loading the full mailbox in memory
, 2) streaming FETCH responses instead of aggregating them in memory
, and 3) reducing the RAM usage of a base user by tweaking its Garage connectors configuration
Collecting production data will then help priorize other, more ambitious works, on the authentication side, Collecting production data will then help priorize other, more ambitious works, on the authentication side,
on the idling side, and on the email streaming side. on the idling side, and on the email streaming side.