shockrah/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

+ New post

Browse Source 
! No editing pass because lazy
This commit is contained in:
shockrah 2021-07-25 14:39:21 -07:00
parent edc304b5d4
commit eac53753a9
3 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

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

6
pages/index.md
View File

@ -1,6 +1,12 @@
# Definitely not a blog # Definitely not a blog
## I swear ## 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)** ## **[Setting up OBS for streaming or recording](/post/obs-setup.html)**
> _March 19, 2021_ > _March 19, 2021_

8
posts/lewd-lad-infra.md
View File

@ -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. 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. 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 ## Closing Thoughts and Remarks
Apart from Freechat, Lewdlad is easily my favorite project to build out. There is one thing I didn't mention, which is turning off the server given low CPU usage.
It's one of those things hasn't been very complex to actually build out but has definitely been the most visceral. 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.