> Hi,
>
> We have seen sometimes that the ibserver (v 1.0) takes a lot of
> CPU, just after a system reboot.
>
> Seems that it performs some housekeepings, garbage collection,
> uncommitted issues, etc.
>
> During this phase, it is hard to work with the database (slow
> performance, some bugs, etc.)
>
> Sometimes, this phase takes a long time.
>
> Questions:
>
> 1. Is there a way to know when the server finishes this phase ?
> 2. Is there a way to accelerate and/or cancel this phase ?
> 3. How can we avoid this ?
>
> Thanks,
>
> Menashe

This is unlikely to be the fbserver. Directly after reboot the server is
lying dormant waiting for a connection from a client. The client connects
and thee may be some activity as requested by the client. But none initiated
by the server. Directly after reboot, the server would't of it's own account
even know what databases are around or where they are on the disk. It has to
be directed by the client to go find one in a particular place.
Can you explain more about this activity and exactly when it is initiated?
More likely to be when you make the first client connection.
Alan