4 ms·
This exactly highlights my fear of widespread use of LLMs for code - missing the actual optimisations because we’re stuck in a review, rather than create, mode
by Fizzadar 2y ago
This exactly highlights my fear of widespread use of LLMs for code - missing the actual optimisations because we’re stuck in a review, rather than create, mode of thinking.
But maybe that’s a good thing for those of us not dependent on LLMs :)
- raybb 2y agoWell if you or anyone else that has good optimization and performance chops http://openlibrary.org/ http://openlibrary.org/ has been struggling with performance a bit lately and it's hard to track down the cause. CPU load is low and nothing too much has changed lately so it's unlikely to be a bad query or something. Main thing I've suggested is upgrading the DB from Postgres 9, which isn't an easy task but like 15 years of DB improvements probably would give some extra performance.
- dgacmu 2y agoIt might not be as awful as feared? That big a jump probably requires a dump and restore, but maybe it could still be done in place. pg_upgrade is pretty solid. But I agree - it's likely a cheap and easy perf win.
- tylerhou 2y agoIs there source code / a GitHub link with more information?
- raybb 2y agohttps://github.com/internetarchive/openlibrary https://github.com/internetarchive/openlibrary
- tylerhou 2y agoIs there a specific issue with more context? I looked at the repo already but it’s not obvious which operations are slowest / most important to optimize.
- raybb 2y agoUnfortunately the discussion mostly is on their public Slack channel which you have to fill out the volunteer form to join. But there are several more specific issues about performance: https://github.com/internetarchive/openlibrary/issues?q=is%3Aissue+is%3Aopen+performance+label%3A%22Theme%3A+Performance%22 https://github.com/internetarchive/openlibrary/issues?q=is%3...