You probably have a good approach in only looking at the comm time.


I had lunch with one of our network guys, and he said that the only accurate
way, in a Client/Server environment, is to have a network monitor tool
installed on both ends of the connection, so that you can take accurate
measures of true network time.  The more sophisticated the OS, the further
isolated the applications are, and therefore the harder it is for the
application to monitor the actual network time.  I think ADSM makes a decent
try at it, but it is beyond their ability.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Re: client accounting
Author:  INTERNET.OWNERAD at SNADGATE
Date:    1/8/98 11:02 AM


John & Jennifer,
I disregard the communication time in our shop.  The only number I care
about is throughput.  How many bytes were backed up in how many seconds.
Communication time is how ADSM transfers the data from the client to the
server and is one of the internal processes ADSM must perform to accomplish
its task.
Looking at your numbers, they seem to match fairly well, I.E.

dsmaccnt                                           dsmsched.log
=============                                     ==============
Field17=965873 KB / 1024 = 943.24MB,  fairly close to 943.3 MB
Field21=13968 secs --> 3:52:48, again fairly close to 3:52:46

An effective data rate of 965873 / 13968 = 69.15 KB/sec.

(I do subtract the "media wait" time figure from "duration in seconds" to
calculate our effective data rate since most of our backups go directly to
tape.)

Sorry, I cannot resolve the communication time gap between the client and
the server.  Perhaps the values are different between the client and the
server.  I will watch this subject for a good answer.

Hope this helps.

Randall Eggert
MAPCO, Inc.
Tulsa, OK





John & Jennifer Price <jp AT DBTECH DOT NET> on 01/07/98 08:39:49 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Randall Eggert/TUL/MAPCO)
Subject:  client accounting




We recently SET ACCOUNTING ON in an attempt to determine transfer rates
from our clients.
The information in dsmaccnt.log on the server does not seem to be
consistent with the information
in dsmsched.log on the client. For example (info for the same session from
each end):
From dsmaccnt.log
Field17=965873 (backup files sent in KB)
Field21=13968  (duration of sessions in seconds)
Field22=816    (idle wait time in seconds)
Field23=13086  (communicaitons wait time in seconds)
Field24=0      (media wait time in seconds)
From dsmsched.log
Total number of bytes transferred:   943.3 MB
Data transfer time:                2,540.99 sec
Data transfer rate:                  380.16 KB/s
Elapsed processing time:            3:52:46
Looking only at the server side, how am I supposed to calculate an accurate
transfer rate from
what I am given in dsmaccnt.log? Is there any way to get accurate
information without having to
go to each client to retrieve dsmsched.log? Does the central logging
feature of ADSMv3 provide
this information at the server? Does anyone know how fields 22-24 of
dsmaccnt.log are calculated?
Can anyone tell me how to come up with 380.16 KB/s given only the data in
dsmaccnt.log?
HELP!