since images are usually the most bandwidth intensive elements of a web app, does this also mean they pose the heaviest load on the server that has to retrieve them from a db? im thinking of "normal" apps like e-shops and the product images.
| SitePoint Sponsor |
since images are usually the most bandwidth intensive elements of a web app, does this also mean they pose the heaviest load on the server that has to retrieve them from a db? im thinking of "normal" apps like e-shops and the product images.
I need someone to protect me from
all the measures they take in order to protect me
If the images are in the db, then yes that will likely be the heaviest load on the server.
Most apps have the image in the file system with only the link to that file in the db.
Providing the image is served cleanly, ie not going through a script, serving images is likely to load the server less than the db. (typically).
Mike
Images in the DB might be a heavy memory load, but they are not that heavy a processing load. All you are doing is loading the image out of a source (DB or file) and then passing it back to the client. It is not computationally intensive.
Things that can cause heavier processing load would be serialization and deserialization of objects--such as loading an XML fragment into your data structure. Also up there would be formatting massive data grids and the like.
Images on the filesystem (or any static resource really) won't have a huge effect on server load unless you're a very popular site. It's also really easy to move static content like images or videos to a separate server if the load on your app server is getting too high.
Posting Permissions
Bookmarks