The answer is partially dependent on your db, but if you want a rule of thumb, then I suggest the fs. Some dbs really don't perform well when moving blobs in and out of the DB.
Also, you need to fine tune your db and where you place the tables that will hold the blob to minimize IO interference when pulling BLOBs and non-blobs. Think about this way, if your DB needs to read a 10meg file at the same time as it needs to read 100 1KB rows for other requests, you are going to affect throughput if both sets of data live on the same spindles. I would be interested to hear what others say. -----Original Message----- From: Andrew Huntwork [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 16, 2005 3:21 PM To: jug-discussion@tucson-jug.org Subject: [jug-discussion] storing blobs on file system or in db I'm writing this web app that allows users to upload documents, such as word docs, images, etc, and then to download those documents again on request. the documents are not searched, interpretted, processed, version controlled, or anything else. just upload and download. i wonder if there's a general rule on whether one should stick such things into a db or onto the file system. i currently favor sticking them in the db. putting them on the fs seems to interfere with clustering (different files would be on different filesystems). it's also another thing to back up and generally maintain. on the other hand putting them in the db puts extra load on the db and the network. there are a bunch of other issues too. Any ideas? Thanks for any help. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
