开场白及使用 Redfish 进行 gRPC 与 REST 基准测试.pdf

1、Bailey Hollis Texas A&M UniversityJeff Hilland HPE LabsBenchmarking gRPCfor RedfishRedfishAPI used to manage servers and equipmentWide industry backing,evolving scopeRESTApproachable for developers,supports HTTP/1.1 and HTTP/2Payload is human readable,machine capablegRPCPossible new approach for Red

2、fish transportClaimed efficiency gains and improved throughputPayload not human readable(Protocol Buffers/Protobuf)IntroductionProvide data to answer the question:Is gRPC a suitable transport for the Redfish data model?1.REST Server+Client implementation2.Develop Redfish Protobufencoding3.Extend imp

3、lementation with gRPC4.Conduct comprehensive benchmarksTesting MethodologyCreating the Protobuf EncodingProtobuf DefinitionRedfish SchemaGenerating a Redfish LibraryProtobuf DefinitionGenerated Go CodeStoring a Mockup ObjectRedfish MockupProtobuf Message ObjectMockup Object Wire FormatProtobuf Messa

4、ge ObjectJson EncodingProtobuf Wire EncodingResults25.2K18.4K22.4K20.7K21.9K26.5K22.5K26.2K25.1K24.6K35.9K34.8K35.6K36.5K37.3K0.010.0K20.0K30.0K40.0KServiceRootAccountServiceManagerSystemMemoryReq/secAverage Request Rate(Higher is better)Test Conditions:24 Client WorkersPersistent ConnectionsObserva

5、tions:HTTP2 shows modest gains over HTTP1gRPC request rate similar across payloadsJSON encode/decode much slower than Protobuf01020304050ServiceRootAccountServiceManagerSystemMemoryMedian Duration(s)Median Unmarshal Duration(Client)(Lower is better)02468ServiceRootAccountServiceManagerSystemMemoryMe

6、dian Duration(s)Median Marshal Duration(Server)(Lower is better)0102030ServiceRootAccountServiceManagerSystemMemoryCPU Usage/1kReq/secNormalized Client CPU Utilization(Lower is better)051015ServiceRootAccountServiceManagerSystemMemoryCPU Usage/1kReq/secNormalized Server CPU Utilization(Lower is bett