Subject | Re: Server hangs |
---|---|
Author | Alexander V.Nevsky |
Post date | 2003-06-13T11:03:27Z |
--- In firebird-support@yahoogroups.com, "Duleep Sahadevan"
<geocalicut@y...> wrote:
encounter so huge performance degradation to call it "hang". Usually
two reasons:
1. Wrong or badly optimized query which consume all processor
resources
2. Automatically started sweep (after transactions gap reached
pre-defined value, default 20000).
If second - set sweep interval to 0 and include sweep in regular
maintenance procedure. If first - it is rather difficult to catch
using Superserver on database in production if you missed this query
while developing. On Classic it will "hang" only own connection and
you can easily ask particular user what he was doing.
Best regards, Alexander.
<geocalicut@y...> wrote:
> Hello.RAM.
>
> I use firebird 1.02 64 bit on a redhat 7.2 machine having 256 MB
> Sometimes the firebird server hangs and the machine has to beDuleep, I suppose you use Superserver since Classic users never
> rebooted. There are 20 win98 clients connected to the server.
>
> The application has over 230 tables and the current database size
> is around 200 MB
>
> Could someone give suggestions on how to isolate the problem ?
encounter so huge performance degradation to call it "hang". Usually
two reasons:
1. Wrong or badly optimized query which consume all processor
resources
2. Automatically started sweep (after transactions gap reached
pre-defined value, default 20000).
If second - set sweep interval to 0 and include sweep in regular
maintenance procedure. If first - it is rather difficult to catch
using Superserver on database in production if you missed this query
while developing. On Classic it will "hang" only own connection and
you can easily ask particular user what he was doing.
Best regards, Alexander.