home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!agate!ucbvax!lrw.com!leichter
- From: leichter@lrw.com (JERRY LEICHTER)
- Newsgroups: comp.os.vms
- Subject: re: ?Effect of large number of logical definitions?
- Message-ID: <9207241813.AA21858@uu3.psi.com>
- Date: 24 Jul 92 14:17:50 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 27
-
-
- 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?
-
- Logical names are stored in hash tables. The hash tables are fairly large,
- so performance is relatively independent of the number of names in the tables.
- There are SYSGEN parameters (LNMxHASHTBL, for x = P for process, S for system)
- that you can change if necessary.
-
- One curious thing about logical name tables: While you see many different
- tables, internally they use one shared table for all system names, and
- one for each process. The stored entry shows what table a given name is
- in. To look up a name, you have to find a match on both the name and the
- table.
-
- Beyond the time cost, the names themselves (and, of course, the tables) have
- to be stored. That will cost you paged pool.
-
- The 100 logical names that GKS adds should be no big deal. The logical name
- facility was designed with exactly this kind of use in mind.
-
- -- Jerry
-
-