
Displaying and Resetting Update Statistics
To access the Administration of the Update System, from the initial screen of Update Management (title bar
Update Requests: Initial Screen ), chooseTo view the update activities on the server you are currently logged onto, choose
Statistics. The statistics contain all of the data collected as of the last reset or server restart.
To reset the statistics, choose Reset ® Statistics. You can now specify whether the statistics are to be reset only on the application server you are currently logged onto (local), or on all servers (global).
The statistics are divided up into the following sections:
Update Requests
Update requests | |||
generated |
1 |
executed (V1) |
15 |
started (V2) |
2 |
executed (V 2 ) |
2 |
canceled |
0 |
deleted |
16 |
Update is active | |||
The client is displayed on the left and the server on the right. The
update request is sent from a dialog or batch work process (client) on the application server you are working on (see status bar) to the update work process (server), which may be running on a different application server.The 1st line specifies how many update requests were
generated by the client (in other words, sent to the server), and how many were processed by the update work process ( executed (V1) ). This number is higher because you are on the application server on which the update server is running - this also processes update requests from other application servers.
If you call up the statistics on a server on which no update work process is running,
As described in the section entitled
The Update Process, the update work process passes the V2 update modules onto a V2 work process - in other words, the 2nd line contains the update work process of the clients and the V2 work process of the servers. Furthermore, both V2 updates were carried out.In the 3rd line you can see how many update requests were canceled by the client, and how many were deleted by the server.
The 4th line indicates whether the update is active (see also
Deactivating and Reactivating Updates).Database Accesses
DB I/O |
B ytes written |
B ytes read |
in total |
456 |
119949 |
min |
28 |
28 |
avg |
152.000000 |
325.065041 |
m ax |
356 |
1172 |
This section logs the database accesses made as a result of the update: total number of bytes written and read, the smallest and largest packet, as well as the average size. This is, therefore, the data that is written to the update tables VBHDR, VBMOD, VBDATA and VBERROR.
Times
Times |
Execution (V1) |
Execution (V 2 ) |
Read |
Write |
Number |
17 |
2 |
375 |
3 |
total (sec) |
9.734802 |
6.046222 |
2.349286 |
0.113074 |
min (msec) |
46.373000 |
3006.741000 |
0.125000 |
32.659000 |
avg (msec) |
572.635412 |
3023.111000 |
6.264763 |
37.691333 |
max (msec) |
3613.746000 |
3039.481000 |
355.894000 |
44.082000 |
kb /sec |
50.306175 |
3.938240 |
This section contains information on the time required to execute the update requests.
1. Column 1: number of V1 update requests executed, the total time required for these in seconds, as well as the shortest, average and longest time required in milliseconds.
2. Column 2: the same information as column 1 but, in this case, for V2 updates.
3. Column 3: number of read operations (updates tables in the database), the total time required for these in seconds, as well as the shortest, average and longest time required for a read operation in milliseconds.
4. Column 4: the same information as column 3 but, in this case, for write operations
Times |
Update |
Commit Times |
Delete |
Number |
5 |
42 |
54 |
total (sec) |
0.183918 |
1.248347 |
0.283877 |
min (msec) |
3.770000 |
0.217000 |
2.474000 |
avg (msec) |
36.783600 |
29.722548 |
5.256981 |
max (msec) |
122.488000 |
188.723000 |
66.108000 |
This section contains the time intervals required for the different steps (minimum, maximum, and average values). Update table updates (column 1), commits and delete operations in the update work processes.