pull down to refresh

31 sats \ 7 replies \ @k00b 3 Apr 2022 \ parent \ on: Daily discussion thread

So happy.

I made the front page query much faster yesterday after fixing 2 things:

  • removing the sub-query and replacing it with a join
  • fixing a hack that I implemented wrong and was causing the front page query to execute twice when loaded

I made comments much faster today by using a lateral join of the subquery instead of a normal join ... when using the normal join I had to compute the entire subquery (very expensive) , but with the lateral join I can filter the subquery for just the stuff that I want (children comments) ... I did still have to use a subquery because the comments query is recursive and you can't use aggregates in a recursive query (but you can in a subquery).

write
preview
0 sats \ 3 replies \ @BlokchainB 3 Apr 2022

What’s the difference better post and recent?

reply
1 sat \ 1 reply \ @k00b 3 Apr 2022

Do you mean top? Recent are recent posts (sorted by time). Top are the posts that did the best for a give period of time

Post takes you to a form to create a new post

reply
0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 1 reply \ @k00b 3 Apr 2022

There are still 2 queries that can probably be improved a lot:

  1. determining how much a user has stacked - we currently sum up all tips they've received to do this ... we should just denormalize this ... this will shockingly save us >50ms per request for mature users
  2. denormalizing some of the notifications
reply
0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author