@matigo you don't cache the number stars on the posts table? just +1 on an insert to post_stars and -1 when you're removing a star. you can even use a trigger if you want (i usually do it in the app)
@matigo Huh. I've always implemented stars by making a stars table and just querying that table for information. stars_count as a COUNT(*) cache on the posts table if necessary. It's never been a problem in the apps I've made…?
@matigo I'm still on Sakura. The AWS services I use are SES for sending e-mail and CloudFront for CDN / caching at the edge. I use a t2.medium as a staging server that is only online for maybe 10% of the month, and that's roughly equivalent CPU-wise to the 2G VPS I'm using at Sakura
@matigo no, they gradually accrue. t2.micro starts with 30, and earns 6 per hour, up to 144:
Each T2 instance starts with a healthy initial CPU credit balance and then continuously (at a millisecond-level resolution) receives a set rate of CPU credits per hour, depending on instance size.
@matigo Well, the initial import may have used it all up, if you did that. There are more metrics you should take a look at -- I don't have a RDS thing handy right now but it should be there somewhere
@matigo 20 GB gives you a baseline performance of 60 I/O operations per second, bursting up to 3,000 while you have the credits. Maybe you've exhausted the burst credits?
@matigo Hm. What do the metrics look like? Maybe you're running low on IOPS credits? How much provisioned storage do you have?
@matigo hm. Cant find the posts now. Could've been a browser bug. I'll investigate when I notice it next time.