Using a database to store images adds software layers to access the image data. The new software layer here is the database itself. Obviously, there are some cache systems on databases, but there are also on file systems, so loading an image from the database would use both caches, each one being independant. In other words, including image files in databases is probably more CPU, memory and disk intensive than just using simple files.
I can understand there are reasons where it is more interesting to use database than simple files. After all, using two systems for data management might become difficult to maintain on large databases. However, I believe using files is more interesting from the performance point of view.
thanx for your reply, kwa.
im just tire of manage my photo :lol:
this is what i thinking if we add a function to auto-saving photos in db by urls, that will be very easy to backup blog,but as you said that mightn't be a good idea...
General Support
b2evolution CMS Support Forums
Using a database to store images adds software layers to access the image data. The new software layer here is the database itself. Obviously, there are some cache systems on databases, but there are also on file systems, so loading an image from the database would use both caches, each one being independant. In other words, including image files in databases is probably more CPU, memory and disk intensive than just using simple files.
I can understand there are reasons where it is more interesting to use database than simple files. After all, using two systems for data management might become difficult to maintain on large databases. However, I believe using files is more interesting from the performance point of view.