On Fri, May 11, 2001 at 11:39:32AM -0700, Eric J. Schwertfeger wrote:
> 
> Aside from what's in the manual, I have a little to offer.  I just
> got InnoDB working yesterday, so take what I have to say with a
> grain of salt.

And I'll add a bit, too. :-)

> Gemini: Currently in Beta testing, with no source code available.

The code *was* in the MySQL bitkeeper repository at one point. I
thought it still was.

> You might be able to get in on the beta program.  I did, I figured
> we could test it using Linux emulation on FreeBSD.  Boy, was I
> wrong.  Not blaming NuSphere, however.  I was just quite surprized
> when the remote install hung.  After going into the area with the
> server, I found that some part of the install had triggered a halt
> on the server.

Yuck.

Yes, I was also hoping for FreeBSD support. But NuSphere needs to see
significant demand for it. On the other hand, once it's released and
the source code is there, making it work on FreeBSD might not be a
huge chore. It already runs on Solaris, Linux, and Windows, right? :-)

> InnoDB: Some little voice inside my head is saying it's too good to
> be true.  I wrote a program to take about a months worth of our live
> data (750K records) and stuff it into a database with a perl script
> via DBI.  InnoDB ran about 50% faster than MyISAM, and about 18
> *TIMES* faster than PostgreSQL.  I wasn't expecting InnoDB to be
> faster than MyISAM, since InnoDB is transactional and MyISAM isn't,
> which is one of the reasons everyone uses to explain why (and when)
> MySQL is faster than PostgreSQL.

InnoDB is pretty impressive, isn't it?!

> A few other differences: Gemini doesn't support BLOBs, and InnoDB is
> limited to 8000 byte BLOBs.  Gemini is limited to 2G tables, and I'm
> not sure about InnoDB.  You can have multiple InnoDB files, but I
> don't know if a table has to reside entirely in one file.

Gemini's BLOB support was supposedly just implemented. I'm told it'll
be part of the next beta cycle (roughly a week fro now, or so?).

Gemini also has smaller maximum key sizes than MyISAM tables. This was
a big issue for us, but they're working on removing that limitation.

And the table size limits aren't supposed to be an issue much longer,
either. Come to think of it, I know the recovery log had that limit,
but I didn't think/know the tables did. I thought that was purely an
OS issue--as it is with MyISAM.

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878    Fax: (408) 349-5454    Cell: (408) 439-9951

MySQL 3.23.29: up 130 days, processed 803,952,600 queries (71/sec. avg)

---------------------------------------------------------------------
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

Reply via email to