pull down to refresh

5 sats \ 3 replies \ @k00b 31 Mar 2022 \ parent \ on: Daily discussion thread
Oh man, I've started actually looking at query performance and have already found 4 really bad ones.
write
preview
0 sats \ 2 replies \ @k00b 31 Mar 2022
DB is also using a lot of CPU as of yesterday too (unrelated to queries because queries haven't changed). Lots to do
reply
4 sats \ 1 reply \ @k00b 31 Mar 2022
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
22 sats \ 0 replies \ @k00b 31 Mar 2022
The AMA made the DB scream
https://snimgs.s3.amazonaws.com/cpus.png
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