Re: [Slashcode-development] many images in the db...

[James M. <jm...@tr...>]

Hi all,

To close the loop on my past email about images in the blob
database---the problem was operator error, as usual.
  
I've upgraded MySQL, moved to Linux 2.6, and fixed some other things.
Indeed, using the INNODB engine for the blob table works (it helps if
you have a version of MySQL that includes InnoDB...).  One caveat is
that you have to make sure that you've set up the table space properly
in the my.cnf file, as noted by Eric Dannewitz below.  Specifically,
in my case I have 8G or so of images, so far, so I've commited three
4000M files, plus one more autoexpanding file to the InnoDB table
space.  I figure that should cover my needs for the next two years of
digital pics (unless I get a new camera with larger data files).

So if you're a nutter like I am and happen to be using Slash as a back
end engine for organizing your digital pics, add an InnoDB tablespace
management step to your configuration process, and then keep an eye on
the InnoDB autoexpanding file to be able to add more space when it
bumps up against your filesystem limit.

As to serving images, I see no perceptible speed differences between
fetching a filename and serving that versus fetching and serving the
blob.  And for processing images, I think it is a touch faster, since
ImageMagick can access the binary immediately rather than having to
read the file in, but again, the difference is unnoticeable.

James
  
At approximately Thu, Jun 10, 2004 at 11:20:34AM -0700, Eric Dannewitz wrote:
> 
> So wouldn't creating a couple more datafiles solve the problem then?
> 
> Shane wrote:
> 
> >
> > On Jun 10, 2004, at 1:40 AM, Eric Dannewitz wrote:
> >
> >> Wouldn't putting them into Innodb files solve the problem?
> >
> >
> > The schema for slash::blob uses TYPE = InnoDB by default...
> >
> > http://cvs.sourceforge.net/viewcvs.py/slashcode/slash/plugins/Blob/ 
> > mysql_schema?rev=1.8&view=auto