Subject | Re: 100% CPU on Windows XP |
---|---|
Author | pivosz |
Post date | 2008-02-27T13:57:28Z |
--- In firebird-support@yahoogroups.com, "Adam" <s3057043@...> wrote:
I tried to set sweep interval to 1000, I ran manual garbagge
collection a restore backup of DB (1,7 MB after restoration)
Processor load is down 0% until I ran application that connect DB for
one time per 10 seconds over ODBC, then CPU load goes to 50-70%. This
load makes FBSERVER.EXE with writes do DB.
Could problem be in ODBC driver (v 1.2) ?
Ivo
>Thank's for your answer.
> --- In firebird-support@yahoogroups.com, "pivosz" <vaclavek@> wrote:
> >
> > Hi,
> >
> > I am using Firebird 2.0.3 SuperServer on Windows XP Professional and
> > Firebird ODBC driver 1.2.
> >
> > First aplication reads and writes data to 1 of 4 tables in database
> > using ODBC. There are about 10 operations / minute.
> > Second web app. writes to this table data under 1 row/min
> >
> > DB size is cca 50 MB, backup 820 Kb.
> >
> > Why is processor load about 98-100% ?
>
> Something would seem amiss here. Your description of the environment
> shows what should be a very bored database server. Also, I have never
> seen a backup file be 50 times smaller than the original. It all
> points to your database being full of obsolete record stubs awaiting
> garbage collection. How big is the database immediately after it is
> restored? And for that matter, does performance return to a reasonable
> level when using a newly restored backup?
>
> If so, I would look very carefully at your applications to make sure
> that they are not holding transactions open for extended periods of
> time. This sort of thing blocks garbage collection, and given enough
> delays will make the database unusable.
>
> Adam
>
I tried to set sweep interval to 1000, I ran manual garbagge
collection a restore backup of DB (1,7 MB after restoration)
Processor load is down 0% until I ran application that connect DB for
one time per 10 seconds over ODBC, then CPU load goes to 50-70%. This
load makes FBSERVER.EXE with writes do DB.
Could problem be in ODBC driver (v 1.2) ?
Ivo