Hey all—wanted to provide a short update now that Discourse has been live for about 24 hours. Hopefully no one is noticing any slowness or other weird forum behavior! (If you are, please drop a note below describing what you’re seeing so I can investigate.)
After 24 hours, our self-hosted Discourse instance has had almost 100 readers sign up! (You can see the list right here.) We’re also about to cross the 100-posts-created threshold, too. Thanks for participating in our launch!!!
The server underpinning our copy of Discourse is an AWS r7g.large EC2 instance (details), with two Graviton3 vCPU cores and 16GB of RAM. We sized this for hurricane-level traffic, and right now, the box is cruising along without even breaking a sweat. Memory usage is very good, and we’re basically serving everything out of RAM right now, which is also very good.
For the technically minded, here’s a screenshot of htop, showing Discourse’s pile of processes and how much RAM and CPU they’re using:
(Discourse exists as a pile of orchestrated Docker containers, and the primary containerized applications are PostgreSQL for the database, Unicorn for the application web servers, sidekiq for job scheduling, and nginx as a reverse proxy. All are visible in the screenshot.)
So please feel free to settle in and get comfortable, 
some posts, and enjoy the forum. At least so far, nothing’s in danger of falling over and breaking!
(And, again, if you do see see something weird, please post below and let me know. The whole team here is committed to making this shift to Discourse as easy and problem-free as possible for everyone!)