Re:File Attachments: Databases can now store files and images
by tomnipotent on Wednesday August 30, 2023 @02:26PM
(#37326656)
> Disk space is cheap
Disk I/O less so. An average RDBMS writing a 10MB BLOB is actually writing at minimum 20-30MB to disk - once to journal/WAL, once to table storage, and for updates/deletes a third copy in the redo/undo log.
You also get a less efficient buffer manager with a higher eviction rate, which can further exasperate disk I/O.
Re:File Attachments: Databases can now store files and images
by crooked-v on Wednesday August 30, 2023 @02:32PM
(#37326735)
But if the files are important enough that you need transactional updates or point-in-time recovery for them, you're stuck with the equivalents of those things anyway, wherever those files end up, plus the extra overhead of coordinating two systems.
Re:File Attachments: Databases can now store files and images
by ltbarcly3 on Thursday August 31, 2023 @07:50AM
(#37335746)
But there is a hard limit to db scale up and you don't want to hit it. Also, who said you need transactional updates or pit recovery in all cases?
Re:File Attachments: Databases can now store files and images
by ransom1538 on Wednesday August 30, 2023 @03:40PM
(#37327843)
Disk space is cheap. Slap on a db, now you got cpu, memory + an entire db OS inside an OS. Now its an expensive mess.
Disk space is cheap, even when it's on a DB server and not S3. Why worry that much about it?