Open topic with navigation

TIBCO Rendezvous® 8.8.0

# Interpreting the Report

This section describes the output from `rvperfm`.

First, `rvperfm` outputs a header, version information, and a summary of its configuration parameters.

Next it polls the network to discover existing `rvperfs` processes. Each `rvperfs` process resets itself and signals its readiness to participate in a new run. When `rvperfm` receives the ready signals, it prints an identifier for each participating `rvperfs`.

`rvperfm` prints a brief string as it begins sending the run of messages, and another when it finishes sending the run. Then it outputs its run report:

Procedure

| 1. | Statistics that `rvperfm` collects while sending the messages.

| 2. | Statistics that each `rvperfs` process collects while receiving messages. Each group of statistics represents the performance of one `rvperfs` process.

## rvperfm Example Report

The annotated `rvperfm` transcript in Report from rvperfm shows the result of a run with one `rvperfs` process receiving the messages.

Figure 143: Report from rvperfm

## rvperfs Example Report

The excerpt in Report from rvperfs illustrates the output of `rvperfs`. First, the `rvperfs` process reports its configuration parameters. Next it outputs its globally unique inbox name, by which you can identify it in `rvperfm` reports.

Then `rvperfs` reports a reset message from `rvperfm`, signaling the start of a run. At the end of the run, `rvperfs` reports its statistics.

Figure 144: Report from rvperfs

## Certified Delivery Agreements

When the performance programs use certified message delivery, `rvperfm` prints information about registration requests in its output; for example:

rvperfm

    Resetting receivers
     Reset acknowledgment received from _INBOX.0A65034A.DEA3B32324F8085470.2
     CM registration request received from rvperfs
     Number of receivers 1

Similarly, `rvperfs` prints information about certified delivery registration in its output:

rvperfs

    Ready...
    Reset received from _INBOX.0A6503F6.11D3B3241239116F0.2
    CM registration received from rvperfm
    Test message received
    Run beginning...

## Elapsed Time

Both programs in the performance tool report the total time that elapsed in each complete run. The speed at which the Rendezvous daemon can deliver messages to the network depends on the network itself, the network interface card (and other hardware parameters), and the host operating system. If `rvperfm` sends at a faster rate than the network can accept, `rvperfm` retains messages in its outbound queue until the network can accept them.

    Sending complete
     Elapsed time:               9.737 seconds

In this example, 9.737 seconds elapsed from the time that `rvperfm` sent the first message of the run, until the time that the daemon transmitted the last message of the run to the network.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2025. Cloud Software Group, Inc. All Rights Reserved.