Hi,

IFX 11.50 FC5W4* HPUX

With some frequency I identify sessions waiting for the nsf.lock mutex .
This wait occur into "sendsocket" function (onstat -g stk)
What I already read about this wait mutex,* can occur when have more than1 cpu vps.

In this case we have 12 cpus.

This behave can have some relation with the configuration bellow?
NETTYPE soctcp,3,250,CPU
(configured to CPU, not NET)

Regards
Cesar

On 03/10/2010 18:20, Cesar Inacio Martins wrote:
How many active sessions?

And you should really be running on NET VPs.

Hi Jonny,

Is around of 400-500 sessions.

Cesar

--- Em dom, 3/10/10, JonnyTDI (AT) Usenet-News (DOT) net <JonnyTDI (AT) Usenet-News (DOT) net> escreveu:

De: JonnyTDI (AT) Usenet-News (DOT) net <JonnyTDI (AT) Usenet-News (DOT) net>
Assunto: Re: nsf.lock mutex wait
Para: informix-list (AT) iiug (DOT) org
Data: Domingo, 3 de Outubro de 2010, 16:20

On 03/10/2010 18:20, Cesar Inacio Martins wrote:
How many active sessions?

And you should really be running on NET VPs.
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list

On 3 Oct, 18:20, Cesar Inacio Martins
<cesar_inacio_mart... (AT) yahoo (DOT) com.br> wrote:
http://www.iiug.org/resources/faq/ifaq06e.htm.1#6.74

The nfs lock is used as part of the system to allow a specific file
number to be duplicated to all of the VPS.
It comes into play most often when a new socket/tli connection has
been established and the other VPs need to be able to write to that
socket.

The most important thing that you can do to gather information about
the problem is "onstat -g ath", "onstat -g stk all", "onstat -g lmx",
and "onstat -g wmx"

Cna you post the output from these? What exact hardware is the running
on? How fast are the cpus?