You may get to a point where there is so much traffic in the SQL server that the rest of the website slows down or stops responding. I would use a cdn or set up a separate server to serve the static images. Note that google recommends using a different domain name for images (like images.mydomain.com) so you don't send the cookies that are sent with the requests to the main domain, and your browser can retrieve them in parallel with the web content.
At 08:41 AM 10/19/2011, you wrote: >Can anyone shed some light on this issue for me? I was originally >storing some images in a database, but then I convinced myself that >it wasn't the most efficient way to deliver the images, so I >switched my solution to static files. > >In general, can someone walk me through the pros and cons of placing >images that will be accessed heavily in a database versus keeping >them in static files? What I'm most curious about is: > >1) When I use a .cfm page in the image tag (< img >src='getImage.cfm?id=282828'/ >), is it cached within browsers just >like a static file? > >2) Is it too much strain on the database to be constantly requesting >5k - 60k blobs? > > >Maybe I should just punt and start using Amazon S3? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:348259 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
