What we forgot to mention and is maybe of importance:
Maxdb version: 7.5.14
OS: linux
On Mon, 2005-05-23 at 11:23, Ronald Van De Walle wrote:
Dear list,
We notice a serious degradation of MaxDB performance when a table is
accessed by a stored procedure many times concurrently.
This is what we see : When executing "SELECT LOCKMODE, LOCKSTATE,
ROWIDLENGTH, ROWID, TABLENAME, LASTWRITE FROM DOMAIN.LOCKS" over 2000
lock entries on the table occur. At the same time, the temporary data
area grows massively (over 1 GB) during which time the whole database
becomes almost unresponsive.
This table holds temporary results from stored procedures, so many
inserts/updates/deletes occur concurrently. To maintain database
session integrity, every set of rows in the table belonging to one
session has its own unique sequence number.
Questions :
1. Why does the temporary data area grow so heavily ?
2. How can we solve the problem of the locks on the table ?
3. Is there a way to obtain more information about what is written to
the temporary data area ?
4. Can we use the ROWID column in DOMAIN.LOCKS to join with rows in our
table ?
Thanks in advance. Regards,
--
Ronald van de Walle - Verzekeringen NV
Oostkaai 23
B-2170 Merksem
Tel. : +32 3 641 66 71
GSM : +32 485 600 023
www.verzekeringen.be
____________________________________________________________________
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* System Engineer, Verzekeringen NV *
* www.verzekeringen.be *
* Oostkaai 23 B-2170 Merksem *
* 03/6416673 - 0477/340942 *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
