title: Storing very small audio/image files in SQLite database via BLOBs?
body: <p><strong>Background Info</strong></p>
  
  <p>I'm new to Android development and I'm creating an Android app for my clients, and I'm trying to figure out the best approach to storing a large amount of audio and image files for my app. The approach needs to fulfill the following requirements:</p>
  
  <p>1) Allow users of the app to add their own images and audio files to the app (which uses a SQLite database). This potentially means that thousands of audio and image files will be stored, but again, they are no larger than 0.35 mb, and most are less than 0.1 mb. Users will likely be uploading bunches of files on the order of several dozen images and a quarter as many audio files. </p>
  
  <p>2) Allow users to sync their local data with a SQL database on a server so that the images and audio files (in addition to allot of other data) can be uploaded, downloaded, and deleted by users of the app at different locations. </p>
  
  <p>I'm aware that it is almost always preferable to store the file paths inside a SQLite database, rather than storing the files as BLOBS, but, as in these questions, <a href="https://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay">BLOB vs. file path storage</a>,
  <a href="https://stackoverflow.com/questions/4387490/your-reasons-to-store-blobs-less-than-0-3-mb-in-database">Storing small BLOBs in a Database</a>,
  there's some situations where storing the files directly in the database is more appropriate, especially so when the files involved are very small, as they are in my app. None of the files in my app are larger than 350 K/b.</p>
  
  <p><strong>My question is</strong>, when dealing with very small file sizes (none of my image/audio files exceed 350 k/b and most are in the 0 to 100 k/b range) but lots of files, is storing images directly as BLOBs rather than file paths going to cause any severe performance hits (as in ore than a few minutes) when users need to upload files to the local SQLite database or when users need to sync the local SQLite database to the remote server? </p>
  
  <p>Lengthy installation times for the app and the initial sync with the remote database are not a problem as long as installation and sync doesn't take a crazy amount of time, say, longer than 45 minutes. </p>