From b18c00bf9492c8cc311d12b874ea8fc43d2871dc Mon Sep 17 00:00:00 2001 From: Ellen Poe Date: Thu, 15 Feb 2024 21:54:55 -0800 Subject: [PATCH] Update to reflect downsized VPS --- airmail_site/src/components/Explanation.vue | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/airmail_site/src/components/Explanation.vue b/airmail_site/src/components/Explanation.vue index a180207..4ca7cfc 100644 --- a/airmail_site/src/components/Explanation.vue +++ b/airmail_site/src/components/Explanation.vue @@ -10,7 +10,7 @@

Airmail has a couple really unique features. It's designed to query against a remote - index and run on inexpensive hardware. The demo server is running on a VPS with 1GB of + index and run on inexpensive hardware. The demo server is running on a VPS with 512MB of RAM. The main search index lives on object storage and is lazy-loaded with range requests. The total cost of the planet demo server is about $10 USD/month, which is fairly low for a planet-scale geocoder. @@ -22,7 +22,7 @@ some compromises. Latency on an Airmail request is pretty high, anywhere from 10ms-10s, depending on how hot the cache is. There's some low hanging fruit for optimization, but S3 range queries are always going to be slower than an SSD random read. If you can afford 350GB of - block storage, you can consistently get sub-50ms latency, and still only need about a gigabyte of + block storage, you can consistently get sub-50ms latency, and still only need about a 512MB of RAM.