Fabric metrics Qi Zhang(IBM Research – T.J. Watson) Hardware Software Fabric Server 32 x Intel(R) Xeon(R) CPU E5-2683 v3 @ 2.00GHz 64GB memory Fabric Client Software Fabric v1.2.0 1 peer, 1 orderer (solo), 1CA Three scenarios compared Default peer: peer running without the metrics component Metrics peer: peer running with the metrics component, the peer reports metrics to a metrics server. Metrics peer(server down): peer running with the metrics component, but the metrics server is down. Results The metrics component introduces only negligible overhead, in terms of both TPS and resource utilization. We use NewBufferedClient as metrics client, which sends metrics to the server every second by UDP. The client is configured to buffer only up to 1432 bytes. Therefore, the memory overhead is negligible when the metrics server is not working. Throughput comparison Committing Endorsing + committing CPU utilization comparison Memory utilization comparison