+ New post

! No editing pass because lazy

.gitignore

@@ -9,3 +9,5 @@ tmp/
 .mirror
 keys/
 *.bin
+
+msg

pages/index.md

@@ -1,6 +1,12 @@
 # Definitely not a blog
 ## I swear
 
+## **[Left Coast Server Bot Architecture Re-Design](/post/lewd-lad-infra.html)**
+
+> _July 25, 2021_
+
+> A casual/technical explanation of Lewdlad's architecture
+
 ## **[Setting up OBS for streaming or recording](/post/obs-setup.html)**
 
 > _March 19, 2021_

posts/lewd-lad-infra.md

@@ -115,10 +115,14 @@ The advantages of Light sail during the "on-season" periods of high traffic are
 This new setup allows me to have instances which can be elastically started/stopped based on their usage which in turn reduces monthly cost.
 
 Regular stoppages can also be configured either from Lambda's side or from an EC2 instance, if we don't want to risk going over the 1000 request quota.
+This should honestly never happen however since that would require somewhere like 30 lambda based commands to be issued _everyday_ for a month straight, which isn't likely given how often commands were issued before the migration.
+At most I would get something like 10 commands a day but it was never consistent and only happened a few times a month, like on the weekends.
 
 
 ## Closing Thoughts and Remarks
 
-Apart from Freechat, Lewdlad is easily my favorite project to build out.
-It's one of those things hasn't been very complex to actually build out but has definitely been the most visceral.
+There is one thing I didn't mention, which is turning off the server given low CPU usage.
+This could probably be fixed by just installing a script on each game server to occasionally log CPU time and check if the server has been "dead" for some time, prompting a shutdown to conserve cost.
+
+There's probably more that could be done but after this point for my current scaling any more feels to much like over engineering so I'll basically keep architecture the way it is now.