Hi

A backup/restore seems to have helped a lot but (still waiting for the rush hours tho)
I remember reading on the web that IB converts records to new versions on-the fly while selecting them and doesn't save the updated version (when metadata changed) - that it only stores new/updated records in the new format leaving everything else in old format forever (or until a backup/restore)
If that's true it would be the reason. I've been changing metadata almost every day for quite a while, so the poor ibserver would have had to iterate throgh several metadata versions for a single record.
I that so?

Thanks,
Marcin

----- Original Message -----
From: Aage Johansen
To: firebird-support@yahoogroups.com
Sent: Monday, December 01, 2003 10:48 PM
Subject: Re: [firebird-support] Who's guilty?


On Mon, 1 Dec 2003 21:26:10 +0000 (UTC), turbomenda wrote:

> I'm running a quite big (over 1GB) database. There are several programs
> and more than 100 users connected to that DB. My problem is the database
> started to work really, really slow (%
> processor usage maxed out throughout the day)
> This obviously looks like an unoptimized query got through to one of the
> client programs (I am doing a large refactoring of the programs recently)


My guess is that you have a long-running (open) transaction.
Can you post the statistscs (from the header page) when your db is slow?

After you check the statistics, get everyone out of the db and either do a
backup/restore or a sweep. With 100 users this may be 'inconvenient', I
know. If the backup/restore cycle 'fixes' the slowness, you'll have to
check (and, probably, change) your handling of transactions in your app
before the problem will go away permanently.
Yoy may be able to find a lot of previous messages on this list concerning
this problem.

--
Aage J.


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


[Non-text portions of this message have been removed]