Interbase 7.5.1 slow after update

Quinn Wildman (CodeGear Developer Support)

2007-03-19 16:25:53 UTC

Try this:

1. Query TMP$Statements (you can do this with Performance Monitor) and
get a list of all active statements when the CPU is pegged.

2. Kick all users out, make 2 copies (not BACKUPS!) of the database.

3. Allow users back in, do the following repeatedly:

a. execute a statement from TMP$Statements against copy1, leave the
connection connected, look at CPU Utilization. OK?
b. If not OK, disconnect, copy copy2 to copy 1. Repeat.

We are hoping for ONE statement that causes the high CPU Utilization. If
you find this, post your results here and we can proceed.

Post by Andre
Before the update, Interbase was crashing once every day. 100+ users
and lots of connections.
Because 7.5.1 update would fix this problem, we updated it.
Result: Interbase does not crash anymore, but is very slow. At 8 'o
clock in the morning, no
problem, but fast getting slower towards 9 'o clock. Server is a dual
Xeon with HTT and Win2003.
CPU is 50% all over the time (single cpu license).
The admin has tried lots of things (htt on/off etc) but could not fix
it.
I tried the tripple ANY_LOCK_MEM_SIZE (to 768kb) and
V4_LOCK_MEM_SIZE,
and after that, the problem is gone!
So why is the default value 256kb and not 768kb? (I read some more
posts about default
tripling these values)
-----------------------
C:\Program Files\Borland\InterBase\bin>iblockpr.exe
Unable to access lock table.
C:\Program Files\Borland\InterBase/SERVER6.lck
operating system directive CreateFile failed
-unknown Win32 error 1224
----------------------
Also when I tried to shutdown the database and Interbase!

--
CREATE DOMAIN NEW_COMPANY AS CHAR(8) DEFAULT 'CODEGEAR' CHECK (VALUE <>
'BORLAND') NOT NULL;