1.6 billion lockreqs

If I have 1.6 billion lockreqs is this going to create a major problem (lag etc) if so does increasing the locks help?

Geezer From The Freezer wrote: > If I have 1.6 billion lockreqs is this going to create a major problem (lag etc) > if so does increasing the locks help? lockreqs is a counter, so there has been 1.6 billion requests for a lock since IDS was started or onstat -z'ed, but that doesn't tell you anything about the actual number of concurrent locks

continued ... more interesting is the ovlock, which counts the number of times maximum number of locks has been reached, and the lockwts which counts counts the number of times sessions waited for a lock. Geezer From The Freezer wrote: > If I have 1.6 billion lockreqs is this going to create a major problem (lag etc) > if so does increasing the locks help?

Claus Samuelsen wrote: > > continued ... > > more interesting is the ovlock, which counts the number of times maximum > number of locks has been reached, and the lockwts which counts counts > the number of times sessions waited for a lock. > > Geezer From The Freezer wrote: > > If I have 1.6 billion lockreqs is this going to create a major problem (lag etc) > > if so does increasing the locks help? ovlocks = 0 lokwaits = 0 System is grinding. In comparison to another server which has the same data and is running fine. Informix 7.31UC5 (up 6 days) on Solaris 8