fix: Upgrade the website's memory limit (#2802)

Some big records were still causing a memory outage for osv.dev, this increases it up to 4Gb's, the maximum memory limit on one core. The osv.dev website only uses around ~1-2 instances, compared to our API which uses 20 instances, and is also using 8Gb per instance, so this is pretty small increase in relative cost. (The gitignore is for the hurl tool, which allows me to send http requests for testing)
google · Oct 29, 2024 · d664cac · d664cac
1 parent 0370501
commit d664cac
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 2 deletions.
diff --git a/.gitignore b/.gitignore
@@ -10,3 +10,4 @@ build/lib
 .history/*
 **/.history/*
 */datastore-helper/
+hurl-scripts/
diff --git a/deployment/clouddeploy/osv-website/run-prod.yaml b/deployment/clouddeploy/osv-website/run-prod.yaml
@@ -25,4 +25,4 @@ spec:
         resources:
           limits:
             cpu: 1
-            memory: 1024Mi
+            memory: 4Gi
diff --git a/deployment/clouddeploy/osv-website/run-staging.yaml b/deployment/clouddeploy/osv-website/run-staging.yaml
@@ -25,4 +25,4 @@ spec:
         resources:
           limits:
             cpu: 1
-            memory: 1024Mi
+            memory: 4Gi