Conversation

Notices

1. Embed this notice
   Kat (kats@chaosfem.tw)'s status on Friday, 02-Aug-2024 01:15:33 JST Kat

   in reply to

   • RevK :verified_r:

   @revk I'll never forget an SQL optimisation moment near the start of my career.

   There was a report whose query would run for well over 11 hours (this was in 1997 or so), and was usually interrupted by the DBMS being shutdown for the nightly backups.

   One day, I took a closer look at the query, and realised two tables had been joined in the wrong order. Fixed that, and it completed in under 5 minutes.

   • Chris Wiegman repeated this.
   • Embed this notice
     RevK :verified_r: (revk@toot.me.uk)'s status on Friday, 02-Aug-2024 01:15:35 JST RevK :verified_r:

     Chasing SQL performance.
     And chasing.
     And chasing and finding the slow queries.
     But no, forget them...
     And down to "that is 0.175s" and well is that a problem"?
     And Oh, fuck, that is done 27000 times each run?
     Let's make that actually two separate queries, each 0.000s or 0.001s
     Fuck that changes things
     SQL is fun.

   • Embed this notice
     Daniel Barlow (dan@brvt.telent.net)'s status on Friday, 02-Aug-2024 01:16:22 JST Daniel Barlow

     in reply to

     • RevK :verified_r:
     @KatS @revk best sql optimisation work I ever did was asking "who receives this report" and emailing them to find out that they never read it. infinitely faster
   • Embed this notice
     Kat (kats@chaosfem.tw)'s status on Friday, 02-Aug-2024 01:19:01 JST Kat

     • Chris Wiegman
     • RevK :verified_r:

     @chris @revk Oof. Thank heavens for managers who understand that people are fallible.