pull down to refresh

I think I'm done with this round of tuning WoT ... we'll go from 100+ fully trusted users to ~10 with a long tail of partially trusted users. The biggest impact of this will be on earning, and on getting a post into the front page without more users upvoting it ... it might be a little too aggressive wrt front paging an item but I can tune it to trust more users if need be.
Oh man, I've started actually looking at query performance and have already found 4 really bad ones.
reply
DB is also using a lot of CPU as of yesterday too (unrelated to queries because queries haven't changed). Lots to do
reply
Plan for speeding up the site which I should be able to do before Miami:
  1. bigger DB instance
  2. if I can't further optimize queries, denormalize some of the data in the DB ... right now two aggregate queries dominate the CPU of the DB: the front page query for items (most of the time is spent counting all votes for items) and counting comments for items ... I hate denormalizing data but it'll work
reply
The AMA made the DB scream The left axis is CPU "demand". The dotted line is the number of CPUs we actually have - 2. The blue in each bar are queries for the front page. The yellow is counting the comments for each item on the front page.
reply