> >Many Thanks.
> >Jerry Apfelbaum
> Interbase/Firebird looks good on paper. But there are a couple of
> things to watch out for.
> 1) Check the Borland Interbase newsgroups for "corruption" to see if it is
> still an issue. I know from reading their newsgroups a few years back ,
> there were quite a few postings. It could of been due to inadequate
> hardware or some external source like a misconfigured server or power
> failure. There are many sites that use IB without such problems but it is
> worth checking it out (especially how to successfully repair a damaged
> IB/FB database because all the tables are stored in one file).
Most of these problems have been fixed in Firebird.
> 2) Speed problems. I don't know how much data your tables will have, but
> IB/FB has a habit of slowing down as more rows are added/deleted.
Really? Howcome there are many people using Firebird without speed
> an automated Sweep process that cleans out the updated/deleted rows
> (deleted & updated rows still take up space until the database is swept).
> Even so a large db will still slow down. I suspect the problem is due to
> unbalanced indexes. The only way to fix it is to unload all your data and
> reload it back in. Some people do it once a week.
That's not true. The sweep process doesn't kick in until there's actually
a problem with long running transactions and new transactions.
> 3) The server CPU load will increase rapidly after the first 5 or 6 users.
> In other words IB/FB requires a much faster CPU than the same number of
> users for MySQL. It is a very CPU intensive DB server.
Most CPU problems are related to the above mentioned problems.
This isn't usually the case. IB/Fb is actually more of a disk-intensive
database engine, because of the ability to use very little memory.
However, Firebird has some new stuff (and IB does too) that allows
it to use more memory when available (and allowed) making it even
>There was an earlier
> problem with IB Super Server not running well on multiple processors (it
> actually slowed things down). I believe this has been fixed in IB version
> 6.5. I don't know if this was fixed in FB because FB may be running IB
> Classic (single processor) version.
"Classic" is not the "single processor" version, it runs much better
on multiple CPUs than the "SuperServer" architecture.
SS still has these problems on multiple CPU machines, Classic does
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL