Re: lock table overflow
The number of locks that you require depend upon the work being performed
and the number of concurrent users doing work.
20k worth of locks is very small in most OLTP environments that I have
worked with. Since you are running out it would be worth increasing. Try
starting at 100k [still low] and see what happens. I have never seen a
significant issue from having more than you need available.
Mark
----- Original Message -----
From: "Bill Hamilton" <bham@finsco.com>
To: "malcolm.iiug" <malcolm.iiug@btopenworld.com>; "informix-list iiug"
<informix-list@iiug.org>
Sent: Wednesday, August 20, 2003 15:04
Subject: Re: lock table overflow
> After bringing the server online for about 2 hours, onstat -p shows"
> ovrlocks = 12
> ovrbufs = 23
> bufwaits = 265372
> lokreqs = 64million+
>
> In onconfig:
> LOCKS = 20,000> BUFFS = 200
>
> Does this seem reasonable?
> If not, what values would be appropriate?
> What other parameters should I check?
>
> > Bill,
> > what is onstat -p showing for ovlocks?
> >
> sending to informix-list
sending to informix-list
On Wed, 20 Aug 2003 16:22:36 -0400, "Mark Denham" <mkdenham@comcast.net> wrote: > >The number of locks that you require depend upon the work being performed >and the number of concurrent users doing work. > >20k worth of locks is very small in most OLTP environments that I have >worked with. Since you are running out it would be worth increasing. Try >starting at 100k [still low] and see what happens. I have never seen a >significant issue from having more than you need available. > >Mark > If I remember correctly, each lock consumes about 40bytes of memory. . . . . . <?>