sengillo@Kodak.COM (Alan Sengillo) (05/02/91)
-- I have a problem when I run informix on a SCO or Interactive system that is running NFS. The problem is that lockd takes up alot of CPU time whenever I do a delete from the database. The surpising thing is that the database is not on the NFS mount. If I turn NFS off, the problem goes away. Has anyone else encountered this problem? The NFS mount is used to mount a directory that is on a SUN. | Alan Sengillo PHONE: (716) 726-9716 or 477-3503 | | Internet: sengillo@Kodak.Com | | USMAIL: Eastman Kodak Co., Dept. 698, 2-1-EP, Rochester NY, 14653-5108 |
jim@tiamat.fsc.com ( IT Manager) (05/04/91)
In article <1991May2.113913@isdc15.Kodak.COM>, sengillo@Kodak.COM (Alan Sengillo) writes: > I have a problem when I run informix on a SCO or Interactive system that is > running NFS. The problem is that lockd takes up alot of CPU time whenever > I do a delete from the database. The surpising thing is that the database is > not on the NFS mount. If I turn NFS off, the problem goes away. Has anyone > else encountered this problem? As I understand it, when you use lockd, all system locks are routed through it. This is so that when a remote system tries to lock a local file, lockd will know if a local process already has it locked. If your SCO or Interactive machine is not exporting any thing via NFS (i.e. you are mounting other system's files to the SCO or ISC box, but NOT the other way), than you can probably take the lockd stuff out of your NFS startup file, and not run it. Also, if you're not exporting anything, and your NFS startup is running mountd, you can stop those, too, and save a few slots in the process table. Good luck. ------------- James B. O'Connor jim@tiamat.fsc.com Ahlstrom Filtration, Inc. 615/821-4022 x. 651
wul@sco.COM (Wu Liu) (05/04/91)
/--sengillo@Kodak.COM (Alan Sengillo) said... | I have a problem when I run informix on a SCO or Interactive system that is | running NFS. The problem is that lockd takes up alot of CPU time whenever | I do a delete from the database. The surpising thing is that the database is | not on the NFS mount. If I turn NFS off, the problem goes away. Has anyone | else encountered this problem? | | The NFS mount is used to mount a directory that is on a SUN. \-- My guess would be that NFS is routing whatever lock requests originate on the system (including those from Informix) to lockd, in case it's a request for a lock on a file that's NFS-mounted. Assuming that the requests take longer to process, don't actually fail, I'd say that things work, although performance will likely be less than optimal. Are you getting failures?
chrisdu@sco.COM (Chris Durham) (05/08/91)
/--sengillo@Kodak.COM (Alan Sengillo) said... | I have a problem when I run informix on a SCO or Interactive system that is | running NFS. The problem is that lockd takes up alot of CPU time whenever | I do a delete from the database. The surpising thing is that the database is | not on the NFS mount. If I turn NFS off, the problem goes away. Has anyone | else encountered this problem? | | The NFS mount is used to mount a directory that is on a SUN. All lock requests go through lockd when NFS is running. We realize that lockd requests are "slow", and that they take up alot of CPU time. We are currently developing a new Network Lock Manager for NFS, which will be included in ODT 1.2, and which will be available as a (S)upport (L)evel (S)upplement (SLS) in the next two months. -- chris durham chrisdu@sco.COM Technical Support ...!{uunet,ucscc}!sco!chrisdu The Santa Cruz Operation "So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then, because you certainly can't rearrange the universe." _Nightfall_ by Isaac Asimov & Robert Silverberg