NYCPHP Meetup

[max goldberg]

Using MySQL as a file server on a large scale is just asking for problems.
I've never heard of it executed well for large numbers of files and it's not
really fit to handle it either.  You don't need to store all the files in
one directory and in reality you shouldn't. There was an informative thread
on NYPHP tittled "[OT] number of files in a directory?" which describes the
hurdles involved with this.

Using InnoDB you should probably be fine, and you will most likely hit 10
million rows of time stamp, camera id, file name before you even see your db
get to 1GB. MySQL is built well enough to handle many GB of data and
hundreds of millions of rows. If you need any sort of concurrency, you are
almost forced to go with InnoDB.

Either way, this is all well within the capabilities of MySQL.

-Cheers

On 1/31/06, tedd <tedd at sperling.com> wrote:
>
> >Keep the images on the filesystem - out of a BLOB record.
>
> Why?
>
> >Map the filesystem, meta data and other stuff into the database.
>
> Isn't there a limit to the number of files that can reside in one
> directory? If so, then how do you handle managing what is mapped
> where?
>
> tedd
>
> --
>
> --------------------------------------------------------------------------------
> http://sperling.com/
> _______________________________________________
> New York PHP Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
> New York PHP Conference and Expo 2006
> http://www.nyphpcon.com
> Show Your Participation in New York PHP
> http://www.nyphp.org/show_participation.php
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20060131/8d99cdab/attachment.html>