Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Esun Kim	9e8a13bb93	Fix by tidy-readability-redundant-control-flow	4 years ago
Esun Kim	e7434d385e	Fix by tidy-modernize-use-override	4 years ago
Esun Kim	6ae8463500	Fix by modernize-make-unique	4 years ago
Vijay Pai	ece1ed7906	clang-format	5 years ago
Vijay Pai	37d248abd0	Remove unused parameter warning (19 of 20)	5 years ago
Guantao Liu	ca541c9c5f	Address review comments.	6 years ago
Guantao Liu	aafa4c48e5	Fix another call of Alarm::experimental()::Set.	6 years ago
Guantao Liu	3b5c470bf1	Clang format.	6 years ago
Guantao Liu	a7a380c69b	Delay the creation of Alarm in the callback-based qps client. The alarm is only used in the fixed-load scenarios, but its construction is a major point of contention in both the closed-loop and fixed-load scenarios. Delay its creation to when it is going to be used, which will get rid of the contention in the closed-loop scenarios.	6 years ago
nanahpang	2d37a7a9b7	Add alarm in callback streaming test There aren't the right set of alarms in callback streaming reactor, so it exceeds the attempted qps while testing the fixed load streaming scenarios in synthetic benchmarks.	6 years ago
Vijay Pai	cdab1c260f	Fix termination condition of streaming callback QPS tests	6 years ago
Vijay Pai	453c6331b6	Fix counters in streaming QPS benchmarks	6 years ago
Moiz Haidry	7bb853ebdd	Addressed PR comments. Made Client::Thread public and removed use of void ptr to refer it. Avoided overloading of NextIssue TIme by renaming it NextRPCIssueTime	6 years ago
Moiz Haidry	5ec78a286d	Added support for fixed load benchmarks, all the rpcs access one requestor to the get the next issue time for the RPC	6 years ago
Moiz Haidry	e6e1081499	Add support for Callback Client Streaming benchmarks	6 years ago
Moiz Haidry	145a3bf91f	Code sanitization	6 years ago
Moiz Haidry	14acde64cc	Addressed Vijay's code review comments	6 years ago
Moiz Haidry	b4d5c7cee4	Benchmark test for callback unary gRPC Every thread intitiates multiple RPCs. The Callback of the unary RPC then issues a new RPC and this goes until the benchmark shuts down. For shutdown the main thread waits on a conditional variable. After shutdown the callbacks increment a rpcs done variable and once the the rpcs done equate the the total number of outstanding rpcs, the last callback performing the increment operation also issues a signal to wake up the main thread. The mainthread process to join the other threads and perform cleanup	6 years ago

19 Commits (d8d1090b9896c2ca718653361ae594910e9a1f7d)