Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Making Postgres slower

byteofdev.com

Post reply on HN
Print view View original

11–20 of 43 posts

Re: Making Postgres slower

#11

Post by don-code »

vichyvich wrote: post #6

I love this! It would be great to have follow-ups and series of books about how to make things worse, as a way to learn to make things better. Maybe it could be like O’Reilly, except the covers could have shittily-drawn fantasy animals, e.g. a 7-year-old’s drawing of a unicorn with a head on each side of its body both talking on their AirPods giving away their money to scammers, making PowerPoint slides, eating too m…

This strategy was actually used during World War II, to ensure pilots could come home safely. Weather forecasting not being what it is today, meteorologists determined what conditions would result in the _most_ lives being lost, then together with mission commanders "designed" missions to simply not meet those conditions.

Source: https://medium.com/butwhatfor/suppose-i-wanted-to-kill-a-lot...

Re: Making Postgres slower

#14

Post by sschnei8 »

gerdesj wrote: post #9

I think this is absolute genius. If you are ever going to get to grips with optimizing something, why not do the opposite first or as a foil? How often do you really fenangle your database (or other system) properly? Are your performance enhancements really based on science or cargo culting or something else?

I always do that when working with a new cloud provider. I spend our Series A as fast as possible after which we can optimize cloud spend!

Re: Making Postgres slower

#15

Post by setr »

don-code wrote: post #11
vichyvich wrote: post #6

I love this! It would be great to have follow-ups and series of books about how to make things worse, as a way to learn to make things better. Maybe it could be like O’Reilly, except the covers could have shittily-drawn fantasy animals, e.g. a 7-year-old’s drawing of a unicorn with a head on each side of its body both talking on their AirPods giving away their money to scammers, making PowerPoint slides, eating too m…

This strategy was actually used during World War II, to ensure pilots could come home safely. Weather forecasting not being what it is today, meteorologists determined what conditions would result in the _most_ lives being lost, then together with mission commanders "designed" missions to simply not meet those conditions. Source: https://medium.com/butwhatfor/suppose-i-wanted-to-kill-a-lot...

The missile knows where it is because it knows where it is not…

https://youtu.be/bZe5J8SVCYQ?si=QrIlpJ6BuJADd_zF

Re: Making Postgres slower

#17

Post by adhamsalama »

vichyvich wrote: post #6

I love this! It would be great to have follow-ups and series of books about how to make things worse, as a way to learn to make things better. Maybe it could be like O’Reilly, except the covers could have shittily-drawn fantasy animals, e.g. a 7-year-old’s drawing of a unicorn with a head on each side of its body both talking on their AirPods giving away their money to scammers, making PowerPoint slides, eating too m…

https://orlybooks.com/

Re: Making Postgres slower

#18

Post by therein »

sschnei8 wrote: post #14
gerdesj wrote: post #9

I think this is absolute genius. If you are ever going to get to grips with optimizing something, why not do the opposite first or as a foil? How often do you really fenangle your database (or other system) properly? Are your performance enhancements really based on science or cargo culting or something else?

I always do that when working with a new cloud provider. I spend our Series A as fast as possible after which we can optimize cloud spend!

Cloud providers love this one trick.
Post reply on HN