| Subject | Re: Firebird performance Sheets |
|---|---|
| Author | Adam |
| Post date | 2008-08-07T01:17:11Z |
--- In firebird-support@yahoogroups.com, "emb_blaster"
<EMB_Blaster@...> wrote:
influencing factors that the information is all but useless. If you
want a ballpark figure, you should be exceeding 10,000 inserts per
second for a prepared query inserting records into a reasonably simple
table.
But add several indices to the mix, add some constraints, add a bunch
of insert triggers to the mix, force your database to compete for CPU
or disk access, chuck a slow network between your client and database
server, make some of the fields really large varchars, hold your
transactions open for so long that garbage builds up etc can quickly
tumble performance.
Without providing many clues about your particular environment, I
can't know whether your experience is expected or indicative of some
other problem. I can assure you there are people on this list that
would consider your 30 million record "huge" table relatively small.
Our largest table (record number wise) is heading towards 10 million,
and inserts are measured in milliseconds (even with a trigger and two
foreign keys to check), so if you are wondering about "minutes" for
hundreds of thousands of records, then there must be other causes.
Can you provide your database engine version as well as the output
from gstat -h?
Adam
<EMB_Blaster@...> wrote:
>The problem with performance sheets is that there are so many
> I´ve thinking...
> There´s many questions about Firebird performance, optimizing, etc...
> But I don´t found one guide to know if a BD is realy slow or not, if
> it (firebird) is running in his fullcharge or is missused.
> There´s one "Firebird performance Sheets", or anyone could post what
> they reached in daily use?
> For example in Firebird Experts Forum someone tell that:
> "... +- 50 Million rows in one table (only one table in database) and
> the size of the file is about 30 GB. There are 8 indexes on it with
> one unique index consisting of 2 fields. Finding a row given the
> unique index values is relatively quick , from a few milliseconds to 2
> seconds the most. My problem is inserts, they are extremely slow. Some
> will go fast and then it will get stuck for easily for about a minute
> on one and carry on again."
> Well, on my DB I had more than 230.000, but it is increasing and
> will become that huge (+-30 million)... will it become so slow too?
> A Firebird performance Sheets should help.
influencing factors that the information is all but useless. If you
want a ballpark figure, you should be exceeding 10,000 inserts per
second for a prepared query inserting records into a reasonably simple
table.
But add several indices to the mix, add some constraints, add a bunch
of insert triggers to the mix, force your database to compete for CPU
or disk access, chuck a slow network between your client and database
server, make some of the fields really large varchars, hold your
transactions open for so long that garbage builds up etc can quickly
tumble performance.
Without providing many clues about your particular environment, I
can't know whether your experience is expected or indicative of some
other problem. I can assure you there are people on this list that
would consider your 30 million record "huge" table relatively small.
Our largest table (record number wise) is heading towards 10 million,
and inserts are measured in milliseconds (even with a trigger and two
foreign keys to check), so if you are wondering about "minutes" for
hundreds of thousands of records, then there must be other causes.
Can you provide your database engine version as well as the output
from gstat -h?
Adam