Aage Johansen wrote:

>
> While records were loaded TaskManager reported (in the "Process" window)
> 11-16% of cpu for the fbserver process, and 4-9% for gbak. The rest was
> mostly the Server Idle process.

That sounds like a database that is disk (or network) bound. Healthy
enough under the circumstances.

> Building an index started out at about 60%, and then quickly rose to 100%
> (and stayed there), but only on one kernel.

That looks OK too. Firebird builds indexes on existing data by reading
it (60%) sorting it, then writing out the sorted data as index pages -
the motion reminds me of crocheting - it creates a level one (leaf)
page, then a level two that points to the level one, then another level
one and a pointer to it in the level two page, continuing until the
level two page is full when it creates a new level three page pointing
the the current level two page, then a new level two page and a link to
it in the level three page, then more level one pages ...

> The indexes aren't declared 'unique', but in practice they are (or nearly so).
> I didn't watch the whole process so I may have missed something.

I don't think that matters...

Regards,


Ann