DSCM Candidate Evaluation Form

A. Tool Information

Provide tool name and version #.

NOTE: Only input about the specific versions cited on the DSCM Evaluation Plan will be accepted.

B. Configuration Details

Provide information about the configuration on which you are running
the candidate:

1. CPU architecture and machine specifics

output from "psrinfo -v"
output from "uname -a"

2. Memory available

output from "prtconf"

    3. Size of the repository (space)

    4. Number of files in the repository

    5. Average number of deltas per file

C. Evaluation Areas

Provide information about your findings in each of the following areas:

1. Operation Functionality

Refer to the Requirements Document for detail.

2. Storage

        To assess storage use during operation, an option exists on the test harness.
        If the -S option is specified, a per-second "df -lk" is run in the background
        during each SCM operation. At the end of the operation, the df output is
        filtered and displayed. The filtering consists of removing headers lines,
      removing data for uninteresting filesystems, and grouping the remaining data
      by filesystem.

3. Performance

Performance information must be in absolute terms (e.g., operation X took
YY seconds to complete).

        Our internal test harness will be posted to the community. Performance data
        should be collected on that set of tests, using whatever hardware you plan to
        work on.

4. CPU Utilization

Timing data from the test harness will be used for now. It is anticipated that
most operations will take five minutes or less.

D. Changes/Features Required/Desired

Provide a list/evaluation of the changes/features desired to be incorporated
into the candidate.

Prioritize the list into two sections:

1. Must Have Initially,
2. Want Eventually.

OpenSolaris

DSCM Candidate Evaluation Form

A. Tool Information

B. Configuration Details

C. Evaluation Areas

D. Changes/Features Required/Desired