Earlier quoted context omitted.
Okay, I looked over our financial statement from 2018, summed a few things up that would be way too boring to provide in detail, and turned the numbers into percentages so that you don't have to do all the math in your head. Here's what I have: 2018 costs: 48% to salaries and contractors (my wife and I are the only people on payroll, and draw $60k salaries for ourselves) 12.1% to operations (health insurance, renting…
I see that you have 4220 members that are subscription holders. I'm supposing that you have more that are active users but not Member/Patron status. What's average sessions? Is there anything you can do with the AWS allocation (ie. AWS configurations or infra swapping)? From my vantage point of what I perceives as your Service model, I'm not readily seeing any component of it that would be CPU intensive, but I'm just…
There's definitely stuff I can do to make AWS cheaper. Starting with just remembering to pre-pay for my instances ahead of time. One of my least favorite things to do is to log into the AWS console, so I try to do it as little as possible.
The CPU intensive part is due to autosave. When a lot of people are writing concurrently (even on the order of hundreds), that was usually what would take down the site in the old days. The site is weird in the sense that there are 10x more writes than reads, and then doing all of the linguistic analysis, badge granting, stats generating cause spikes when they happen as well. I'm @buster on Twitter if you want to continue the discussion there.