To BLOB or Not To BLOB: Large Object Storage in a Database or a Filesystem?

Computer Science – Databases

Scientific paper

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

Scientific paper

Application designers often face the question of whether to store large objects in a filesystem or in a database. Often this decision is made for application design simplicity. Sometimes, performance measurements are also used. This paper looks at the question of fragmentation - one of the operational issues that can affect the performance and/or manageability of the system as deployed long term. As expected from the common wisdom, objects smaller than 256KB are best stored in a database while objects larger than 1M are best stored in the filesystem. Between 256KB and 1MB, the read:write ratio and rate of object overwrite or replacement are important factors. We used the notion of "storage age" or number of object overwrites as way of normalizing wall clock time. Storage age allows our results or similar such results to be applied across a number of read:write ratios and object replacement rates.

No associations

LandOfFree

Say what you really think

Search LandOfFree.com for scientists and scientific papers. Rate them and share your experience with other people.

Rating

To BLOB or Not To BLOB: Large Object Storage in a Database or a Filesystem? does not yet have a rating. At this time, there are no reviews or comments for this scientific paper.

If you have personal experience with To BLOB or Not To BLOB: Large Object Storage in a Database or a Filesystem?, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and To BLOB or Not To BLOB: Large Object Storage in a Database or a Filesystem? will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFWR-SCP-O-568214

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.