[Typo3-dev] thougts of TYPO3 imagefunction and short MD5 Hash

[Kasper Skårhøj]

In addition; Lets say we stored images in the database. For each media
field we would either need to store the files in a serialized array
which means that we had to load the full array each time. Otherwise it
had to be a list of references to another table which is more code to
manage the thing. And the replication deal is off since having a bunch
of references to records holding ONLY the image as a blob OR references
to files is the same.
Finally, most MySQL environments are set up to allow only 2MB large
queries so files could not be larger than that.

I also find that the Zend test does not take into account what the speed
is if there are 10000 images stored in the table compared to 10000 files
in a folder; which one situation is served faster? (Actually 10000 files
in folders ARE slow to access/write!).

At this point we haven't even discussed the additional overhead of
having '... src="serve_image.php?image=...."'; that will load PHP more,
it will be more "cryptic" HTML code (taking more space probably) and
generally raise the chance of more support questions and bugs to fix in
the system.

- kasper


On Wed, 2004-07-21 at 11:40, Leendert Brouwer [Netcreators] wrote:
> > There is another article comparing the storage of files in a database vs.
> > storing files on the file system [1].
> >
> > [1]:http://www.zend.com/zend/trick/tricks-sept-2001.php
> 
> The primary (and only, as far as I can see) advantage mentioned in this
> article is that you can seperate the hardware for the database and the
> webserver. I don't see what storing images in the database has to do with
> that. Sure, you can apply load balancing, thereby having a big dual xeon
> database server and X webservers, but then still, it doesn't matter. The
> webservers are replicated as well, so the images will always be able to
> reference to. Another solution would be to store certain part of the images
> on different "dedicated" servers. In very heavy, specific situations such a
> hardware decision could be made. So, to me the mentioned article from Zend
> does not hold much value. The disadvantages of storing in the DB are much
> too large imho.
> 
> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
-- 
- kasper

--------
Please notice NEW EMAIL ADDRESS for 2004!! (due to SPAM-contamination)
	
"kasper2004 at typo3.com"