Performance Tuning Guide - EMC Community Network

Measuring Performance
9 Unique Object Types Fetched
58 Total Objects Fetched
Fetches Type
1 rim7_record
1 dm_sysobject
1 dmc_wfsd_rim_sdt
23 dmc_wfsd_element_string
3 dmc_wfsd_type_info
1 dm_process
25 dmc_wfsd_element_parent
1 dmc_wfsd_element_integer
2 dm_activity
****** Total number of iscurrent calls per type *****
11 Unique Object Types IsCurrent Called
147 Total IsCurrent Calls
Fetches Type
23 dmc_wfsd_type_info
1 dmc_wfsd_rim_sdt
22 dm_activity
3 rim7_record
21 dm_process
27 dm_workflow
1 dm_relation
3 dmi_package
15 dmi_queue_item
1 dm_user
30 dmi_workitem
The report shows 25 parent objects being fetched (dmc_wfsd_element_string) along with
23 string process variables (dmc_wfsd_element_string) and 1 integer process variable
(dmc_wfsd_element_integer), for a total of 49 fetches. Consolidating the 23 string process
variables and 1 integer process variable into one SDT reduces the number of fetches by 46.
Analyzing query results processing
Query results processing adversely impacts performance as the result set size and query usage
increase. Analyze this issue by inspecting the raw DFC trace files. Look for the following type
of call sequence:
...
EXEC_QUERY RPC, e.g. select r_object_id from …
MultiNext RPC (gets up to 50 results)
SysObjectFullFetch (fist object)
SysObjectFullFetch (2nd object)
SysObjectFullFetch (3nd object)
...
Figure 29, page 77 shows how service times grow when using query and fetch instead of query
and collection.
Note: There can be situations where you cannot query and fetch code pattern.
76 EMC Documentum xCP 1.0 Performance Tuning Guide