[nycphp-talk] LARGE mysql database performance
Jonathan Hendler
hendler at simmons.edu
Tue Jan 31 17:23:22 EST 2006
Keep the images on the filesystem - out of a BLOB record.
Map the filesystem, meta data and other stuff into the database.
MySQL though could handle this app.
Clustering means MySQL is scalable in a way that you aren't too limited
by the database performance.
Keith Richardson wrote:
> So I am writing a "security camera" app at work, and using mysql/php.
> I have the cameras uploading snapshots via ftp to the server.
>
> Now for dealing with the images, and indexing them for easy searching,
> I want to throw the info into a mysql database. I wouldnt mind also
> sticking the image data in the table too, so that you HAD to go
> through the app to view the images instead of direct url linking, but
> was wondering, how does mysql react with a 20-30gb database? would
> this be very bad? I have run a forum that used vbulletin with about a
> 500mb database, but that did not have any issues at all.... but
> 20-30gb is quite the large database :p
>
> Any thoughts or experiences?
>
> --
> Keith Richardson
>
>------------------------------------------------------------------------
>
>_______________________________________________
>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
>
>
More information about the talk
mailing list