Hi, According to InnoDB's page, the largest innodb database is currently a bit over 1TB. This is in Mytrix's database (Mytrix provide site tracking services for your website, see www.mytrix.com).
With a default page size of 16KB, you get a theoretical maximum database size of about 60 TB. You can increase the page size to a maximum of 64KB (though that requires a recompile of innodb) to give you a maximum database size of about 238 TB. Oracle, on the other hand has a maximum file size limited by the OS (usually 4GB) and a maximum of 1024 files per tablespace (again, dependent on OS) which gives you a total size of about 4,000 TB. These are all theoretical limits, of course, and I don't know how they relate to real-world limits, but I would guess that Oracle would scale better than MySQL, especially with you getting so close to the physical limit of an InnoDB table. Dean. > -----Original Message----- > From: Andrew Bryant [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 26 September 2002 7:31 pm > To: [EMAIL PROTECTED] > Subject: Storing 100 million images in the database > > > Hello all, > > This discussion appeared recently: > > >| Can I use MySQL to store pictures as part of a record? > >| Should I just try to store the name of the picture? > >Yep but it depends on the size of the pictures. > > Let me describe a scenario we have here in genomics research, which is > extremely demanding in this respect. > > We have 125 million smallish images (each one is tens of KB, produced by > gene sequencing machines). Currently we store these in tarfiles and > index the images (the offset in the tar file) using an Oracle > database. Each tarfile is around 1.5GB, containing tens of thousands of > images. Thus, by using tarfiles we limit the number of files kept by the > operating system (Tru64 Unix), which would be unmanageable > otherwise. This method has various drawbacks, however, associated with > keeping the database and tarfiles in sync. > > What we're contemplating now is keeping images in the database, and this > re-design is estimated at 5-10TB of (Oracle) database. Does anyone have > a comparable situation, in MySQL or any other realm? As well as > Oracle we use MySQL heavily, partly because it's open source philosophy > has distinct advantages in the public domain research context. > > Probably the closest comparison, at the National Center for Biotechnology > Information in the USA, is to store these images in multiple Sybase > databases, keeping the size of each database down to 250GB. Our re-design > is somewhat similar, but would use Oracle partitioned tables rather than > multiple Sybase databases. > > As you can imagine this re-design is a major project for us, and > comparative examples are potentially very valuable. > > Regards, > > Andy Bryant > Oracle DBA and MySQL novice > Wellcome Trust Sanger Institute, UK > > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <mysql-unsubscribe- > [EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
