Conversation

Notices

1. Embed this notice
   tk (tk@f.kawa-kun.com)'s status on Tuesday, 17-Sep-2024 02:03:00 JST tk
   Is 2 GB too large for an #SQLite database performance-wise? 🤔 #Python
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Tuesday, 17-Sep-2024 02:04:13 JST SuperDicq

     in reply to

     @tk@f.kawa-kun.com That actually depends on a lot of things like what you need the database, how often you query it, what hardware it runs on and how the schema is designed. You really can't say with filesize alone.

   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Tuesday, 17-Sep-2024 02:04:54 JST Sick Sun

     in reply to

     • SuperDicq
     @SuperDicq @tk does it try to load everything into memory?
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Tuesday, 17-Sep-2024 02:10:31 JST SuperDicq

     in reply to

     @tk@f.kawa-kun.com Like honestly you should just look at your queries and how long they take to execute. If they take too long first look at your code if you actually need all those queries and check if you can optimize them by doing smarter joins, reducing the amount of queries through batching inserts or updates, etc.
     
     After all that maybe you should look at a different database solution.

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Tuesday, 17-Sep-2024 02:12:02 JST SuperDicq

     in reply to

     • Sick Sun

     @sun@shitposter.world @tk@f.kawa-kun.com Sqlite doesn't do that by default.

     Sick Sun likes this.