Re: NETTYPE settings (was: Server hangs with "mutex wait ns

Then you could get away with a single listener, but I still would not. During times of heavy load, and especially during a checkpoint (which is always run by a thread in CPU VP #1 where that first listener also resides) you might have trouble getting a shared memory connection for things like running onstat , onmonitor, sysmaster scripts, etc. which might be critical to monitoring what's happening. Art S. Kagel ----- Original Message ----- From: Rich.... Spitz At: 1/31 12:25 > Art S. Kagel wrote: > > > Also I notice that your shared memory NETTYPE only specifies > > one listener poll thread, shared memory listeners should always > > be run in ALL CPU VPs for best responsiveness and to keep > > CPU VP#1 (which handles the first poll thread) from > > running flat out and taking 90% of the work for itself. > > > > Change the NETTYPE settings as follows: > > > > NETTYPE ipcshm,3,50,CPU # Configure poll thread(s) for nettype > > NETTYPE tlitcp,2,300,NET # Configure poll thread(s) for nettype> > What about an engine that has almost no shared memory connections > (dedicated database server) and about 70-80 concurrent connections > over TCP/IP? Machine has 2 processors (Intel PIII 933MHz) running > under Linux. > > Regards, Richard > -- > +-----------------------------+--------------------------------------+ > | Dr. med Richard Spitz | Mail: spitz@ana.med.uni-muenchen.de | > | Klinik fur Anaesthesiologie | Tel : +49-89-7095-6110 | > | Klinikum der Univ. Munchen | FAX : +49-89-7095-6420 | > | 81366 Munchen, Germany | GSM : +49-172-8933578 | > +-----------------------------+--------------------------------------+