home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!caen!deccrl!news.crl.dec.com!news!nntpd.lkg.dec.com!Nephi.Enet.DEC.Com!coar
- From: coar@Nephi.Enet.DEC.Com (Rodent of Unusual Size)
- Subject: Re: ?Effect of large number of logical definitions?
- Message-ID: <1992Jul23.164155.11511@nntpd.lkg.dec.com>
- Summary: Keep on tunin'
- Keywords: VMS, logical names, performance
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Organisation: Employed by (*NOT* speaker for) DEC, Boxborough, MA, U.S.A.
- Organization: Digital Equipment Corp.
- Distribution: comp
- Date: Thu, 23 Jul 1992 17:38:37 GMT
- Lines: 28
-
-
- In article <1992Jul23.143600.3476@rdg.dec.com>, winalski@adserv.enet.dec.com (Paul S. Winalski) writes...
- >
- >In article <1992Jul23.094517.1@woods.ulowell.edu>,
- >welchb@woods.ulowell.edu writes:
- >|>
- >|>What measurable or noticeable effect upon users is caused by having
- >|>a large number of logicals defined in the system tables? I ask this
- >|>because we just installed GKS; it has created close to 100 logical names,
- >|>which will seldom get used.
- >|>Will this slow down the average non-GKS user? Should the designers
- >|>of GKS have used a different method?
- >
- >Little or no effect whatsoever. Don't worry about it.
-
- As long as you let AUTOGEN resize the LNMSHASHTBL (which controls the size
- of the hash table for all shared logical name tables) appropriately. If
- the hash table is too dense, you'll get hit in the performance because of
- collisions and $TRNLNM having to walk the bucket chain.
-
- >--PSW
-
- #ken :-)} Jeratol the Chaotic
-
- Coar@Nephi.Enet.DEC.Com | All opinions herein contained, stated or implied,
- Coar@DECUS.Org | are solely those of the author. And he's fullovem.
- Coar@Eisner.DECUS.Org | `... it was mine art, ... that made gape the pine
- Massachusetts, USA | and let thee out.' - Prospero (_The Tempest_)
-