mySQL physical limits

[djhawthorn]

Hi,

If I wanted to encode several hundred MBs of JPG image files into a mySQL table, would that be asking too much of the DB?

Generally, only one encoded file would be requested at a time, but there could be lots of users hitting it at once. Also, I'd want to (if possible) be encoding things like 5-10MB movie files and stuff as well...

I can spread them out across tables if this helps at all. Any advice (even disuasion) from the above would be appreciated.

 

[Shadowhunter]

If you have a good host, I don't see why it would be a problem at all. Good luck with entering them all in the table though... not that it would be hard, just very time consuming.

 

[rycamor]

This should work, as long as you are careful to configure MySQL properly for large object storage. Don't use a standard MySQL configuration. Research the online documentation, and then edit and copy the correct file into the 'my.cnf' configuration location. In particular, you will want to pay attention to the amount of memory overhead and caching you allow MySQL to access.

Is there a specific reason you need these to be in a database, and not just stored as files? -------------------------------------------

"Calculus is just the meaningless manipulation of higher symbols"
                          -unknown F student