View Poll Results: What would make web app faster in performance when it comes to storing images?

11. You may not vote on this poll
  • Sotre images in the MySQL Database

    0 0%
  • Store images in a secured folder and call them when needed

    11 100.00%
  • Dunno

    0 0%
Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2005

    mysql performance

    We are building a Database for a client. this database will grow pretty big so performance needs to be taken into consideration.
    My question is this, the client wants to store images (one per each account (4000+)) into the mysql database. another developer thinks it should be stored in a non exposed location and call each image when needed as this would make thing smoother and quicker overall.
    the images are around 1MB max.
    what are your thoughts as far as performance for the entire site:
    A) Storing the images in the Database
    b) Storing the images in a secured folder on the server

    GS RichCopy 360 Enterprise - Voted #1 for data migration and replication in terms of performance and features. Replicate data across between servers in the same network, WAS, or even across the internet

  2. #2
    Join Date
    May 2006
    Teh Interweb
    I would definately go with the second option personally. Purely from a mathmatical standpoint, if you have 4000 users and each has a 1MB picture in the DB then you are looking at an almost 4GB database. Not the easiest thing to backup/restore and move if needed.

    My vote is with the developer. Although, if you are designing it for the client and the client wants it the other way, all you can do is suggest your method and hope they bite.

    [[email protected]] ~ $ cat .signature
    cat: .signature: No such file or directory

  3. #3
    Join Date
    Nov 2005
    Palma de Mallorca, Spain
    I would say b) option (in a folder), just because the overhead to *display* should be higher if stored on a database, but the Oracle article made me think twice

    A pair of links if it helps...


    Last edited by juangake; 01-03-2007 at 08:50 AM.

  4. #4
    I'd personally go for option b as well - if there are a lot of images and they are accessed quite often, your server is going to be under quite a bit of load if you store the images in a mySQL db.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts