Re: Insert picture in MySQL using JDBC
Manish Pandit wrote:
IMO you should be storing images on the file system, and serve them
via HTTP or local file system reading - based on the security
requirements.
That is often stated.
It was definitely true 10-12 years ago with a MS Access database.
It is not necessarily true with todays database (as long as the
pictures have a reasonable size).
I actually once made a test with ASP.NET and MySQL (the fact
that it is ASP.NET and not J2EE should not matter much). The
results were:
File (1 threads): 1,9 get per second
File (10 threads): 2,1 get per second
File with web app cache (1 threads): 16,8 get per second
File with web app cache (10 threads): 17,8 get per second
File directly by web server (1 threads): 17,6 get per second
File directly by web server (10 threads): 20,1 get per second
Database (1 threads): 10,7 get per second
Database (10 threads): 11,6 get per second
Database with web app cache (1 threads): 17,1 get per second
Database with web app cache (10 threads): 19,5 get per second
And storing the files in the database together with the meta
data is much easier to manage.
Arne