ca.portal.admin

Re: FW: diagnostics and symbol table

Discussion created by ca.portal.admin on Jan 25, 2008
You do not write where you see the decrease in I/O.

Since the load modules are much bigger in size with the diagnostics and
symbol tables you most likely would not be able to fit them all in memory.
That would result in reloads of the load modules and additional reads from
the laod area or load libraries, depending on how often programs need to be
reloaded this could be a significant amount of I/Os.

The CPU decrease just for turning off the diagnostics and symbol tables is
probably somewhere between 25 and 50%. You would get an additional savings
from not having to continuously load the programs into memory.

Tommy Petersen
110 Cokesbury Rd
Room 542H
Lebanon, NJ 08833

Phone:
Internal 200 - 3699
External (908) 236-3699
Fax: (908) 236-3692




""Rozeboom, Kay
[DAS]""
<KAY.ROZEBOOM@IOW To
A.GOV> IDMS-L@LISTSERV.IUASSN.COM
Sent by: IDMS cc
Public Discussion
Forum Subject
<IDMS-L@LISTSERV. FW: diagnostics and symbol table
IUASSN.COM>


01/25/2008 12:59
PM


Please respond to
IDMS Public
Discussion Forum
<IDMS-L@LISTSERV.
IUASSN.COM>







Here is why I am asking. We discovered that one of our production CV's
had diagnostics and symbol tables turned on for every dialog. The less
said about how that happened, the better. We turned them off for the
most highly-used dialogs (the 80/20 rule) and saw a huge decrease in CPU
used, for a similar number of transactions. However, there was also a
huge decrease in I/O at the same time. So I am trying to figure out
whether or not the change in I/O is related, and who or what gets credit
for the CPU decrease.

Outcomes