Blog announcing us-east-1 (#901)

levkk · web-flow · commit dde5fa886b59 · 2023-08-08T12:59:07.000-07:00
diff --git a/pgml-dashboard/content/blog/announcing-support-for-aws-us-east-1-region.md b/pgml-dashboard/content/blog/announcing-support-for-aws-us-east-1-region.md
@@ -0,0 +1,50 @@
+# Announcing Support for AWS us-east-1 Region
+
+<div class="d-flex align-items-center mb-4">
+  <img width="54px" height="54px" src="/dashboard/static/images/team/lev.jpg" style="border-radius: 50%;" alt="Author" />
+  <div class="ps-3 d-flex justify-content-center flex-column">
+    <p class="m-0">Lev Kokotov</p>
+    <p class="m-0">August 8, 2022</p>
+  </div>
+</div>
+
+Since we released PostgresML Cloud a few months ago, we've been exclusively operating out of the AWS Oregon data center. Some say that the West Coast is the Best Coast, but we firmly believe your database should be as close to your application as possible. Today, we are happy to announce that we've added support for the `us-east-1` AWS region, also known as N. Virginia, or the home base of most startups and half the websites you use on a daily basis.
+
+## Impact
+
+If you've been using our Oregon (`us-west-2`) deployments and decide to switch to `us-east-1` instead, you should be able to see a reduction in latency of up to 80ms. Typical latency between the two coasts, measured with simple pings, isn't very high, but when TCP is used, especially with encryption, every millisecond of additional round trip time is amplified.
+
+To demonstrate the impact of moving the data closer to your application, we've created two PostgresML deployments: one on the East Coast and one on the West Coast. We then ran `pgbench` from a virtual machine in New York against both deployments. The results speak for themselves.
+
+<center>
+
+![us-east-1 throughput](/dashboard/static/images/blog/us-east-1-throghput.svg)
+
+</center>
+
+<br>
+
+<center>
+
+![us-east-1 latency](/dashboard/static/images/blog/us-east-1-latency.svg)
+
+</center>
+
+<br>
+
+## Using the New Region
+
+To take advantage of latency savings, you can <a href="https://postgresml.org/signup">deploy a dedicated PostgresML database</a> in `us-east-1` today. We make it as simple as filling up a very short form and clicking "Create database".
+
+<center>
+
+![new region](/dashboard/static/images/blog/us-east-1-new-region.png)
+
+</center>
+
+## Performance is Key
+
+At PostgresML, we care about performance above almost anything else. Bringing machine learning to the data layer allowed us to remove a major latency bottleneck experienced in typical ML applications, but that's only one part of the story. Bringing PostgresML as close as possible to your application is just as important. We've built our cloud to be region agnostic, and we'll continue to add support for more regions and cloud providers.
+
+
+
diff --git a/pgml-dashboard/content/docs/guides/setup/quick_start_with_docker.md b/pgml-dashboard/content/docs/guides/setup/quick_start_with_docker.md
@@ -4,7 +4,7 @@ To try PostgresML on your system for the first time, [Docker](https://docs.docke
 
 !!! tip
 
-If you're looking to get started with PostgresML as quickly as possible, [sign up](https://postgresml.org/signup) for your free serverless [cloud](https://postgresml.org/signup). You'll get a database in seconds, and will be able to use all the latest Hugging Face models on modern GPUs.
+If you're looking to get started with PostgresML as quickly as possible, [sign up](https://postgresml.org/signup) for our free serverless [cloud](https://postgresml.org/signup). You'll get a database in seconds, and will be able to use all the latest Hugging Face models on modern GPUs.
 
 !!!
 
diff --git a/pgml-dashboard/src/api/docs.rs b/pgml-dashboard/src/api/docs.rs
@@ -80,6 +80,8 @@ async fn blog_handler<'a>(path: PathBuf, cluster: &Cluster) -> Result<ResponseOk
         cluster,
         &path,
         vec![
+            NavLink::new("Announcing support for AWS us-east-1 region")
+                .href("/blog/announcing-support-for-aws-us-east-1-region"),
             NavLink::new("LLM based pipelines with PostgresML and dbt (data build tool)")
                 .href("/blog/llm-based-pipelines-with-postgresml-and-dbt"),
             NavLink::new("How we generate JavaScript and Python SDKs from our canonical Rust SDK")
diff --git a/pgml-dashboard/static/images/blog/us-east-1-latency.svg b/pgml-dashboard/static/images/blog/us-east-1-latency.svg
diff --git a/pgml-dashboard/static/images/blog/us-east-1-new-region.png b/pgml-dashboard/static/images/blog/us-east-1-new-region.png
diff --git a/pgml-dashboard/templates/layout/nav/top.html b/pgml-dashboard/templates/layout/nav/top.html
@@ -23,7 +23,7 @@
             </li> -->
             <% } %>
             <li class="nav-item d-flex align-items-center">
-              <a class="nav-link p-0" href="/blog/llm-based-pipelines-with-postgresml-and-dbt">Blog</a>
+              <a class="nav-link p-0" href="/blog/announcing-support-for-aws-us-east-1-region">Blog</a>
             </li>
           </ul>
   
diff --git a/pgml-dashboard/templates/layout/nav/top_web_app.html b/pgml-dashboard/templates/layout/nav/top_web_app.html
@@ -91,7 +91,7 @@
             </li>
 
             <li class="menu-item rounded-0 d-flex align-items-center">
-              <a href="/blog/announcing-gptq-and-ggml-quantized-llm-support-for-huggingface-transformers">Blog</a>
+              <a href="/blog/announcing-support-for-aws-us-east-1-region">Blog</a>
             </li>
   
             <% if !standalone_dashboard { %>
