Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <431850332.14731262581614468.JavaMail.jira@brutus.apache.org>
Date: Mon, 4 Jan 2010 05:06:54 +0000 (UTC)
From: "Philip Zeyliger (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Updated: (AVRO-279) StatsRpcPlugin -- plugin to keep RPC
 stats
In-Reply-To: <2045156349.1262302589397.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AVRO-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philip Zeyliger updated AVRO-279:
---------------------------------

    Attachment: rpc_stats.html
                AVRO-279.patch.txt

Attaching a patch which includes a plugin that records server start/end points for an RPC, and a servlet that displays them.

One of the tests has a main() method which lets one "demo" the output.  Fun to play with.  I've attached sample output here.  It's very ugly.

I've also very naively measured the overhead of the stats collection.  It's not small:

bq. Overhead: 28.7800%.  RPC/s: 3422.781569 (with) vs 4407.859213 (without).  RPC time (ms): 0.292160 vs 0.226868

That said, stats processing is not getting in the way of sub-microsecond RPCs.  And this server is doing absolutely nothing.  The input and output schemas are 'null', so there's not even any parsing to do.

This patch depends on AVRO-271, AVRO-273, and AVRO-275.

> StatsRpcPlugin -- plugin to keep RPC stats
> ------------------------------------------
>
>                 Key: AVRO-279
>                 URL: https://issues.apache.org/jira/browse/AVRO-279
>             Project: Avro
>          Issue Type: New Feature
>            Reporter: Philip Zeyliger
>            Priority: Minor
>         Attachments: AVRO-279.patch.txt, rpc_stats.html
>
>
> I'm working on an RPC Plugin that, when enabled on the transceiver, keeps track of statistics.  It also exposes a servlet for accessing them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.