Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!rochester!cornell!uw-beaver!zephyr.ens.tek.com!tektronix!sequent!mac
From: mac@sequent.UUCP (Cormac Burke)
Newsgroups: comp.databases
Subject: Re: Context Switching
Keywords: Ingres
Message-ID: <48202@sequent.UUCP>
Date: 10 Dec 90 20:51:34 GMT
References: <3844@stl.stc.co.uk>
Reply-To: mac@sequent.UUCP (Cormac Burke)
Organization: Sequent Computer Systems, Inc
Lines: 11

In article <3844@stl.stc.co.uk> "D.S.Riches" <dsr@stl.stc.co.uk> writes:
>
>We've recently hit a problem with running Ingres over a network.
>Our database sits on a Sun 4/280 and runs ingres/bin/lockmgr

Have you considered running the lockdriver instead of the lockmgr?
Don't know if this is the issue with context switching, but it 
should be easy enough to test. It's pretty extensively documented
that the driver works much more efficiently than the lockmgr.
Good luck!
Cormac