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

Tag: Branch: Tree: b6989ff3e4

Author	SHA1	Message	Date
Craig Tiller	8b8f43aecf	[metadata] Remove arena from `grpc_metadata_batch` constructor (#36118 ) Internally, use `std::vector` instead of `ChunkedVector` to hold extra metadatum. I'm not totally convinced this is the right move, so it's going to be a try it and monitor for a month or so thing... I might roll back if performance is actually affected (but I think we'll see some wins and losses and overall about a wash). Closes #36118 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/36118 from ctiller:YUPYUPYUP `68e0acd0a2` PiperOrigin-RevId: 620902195	1 year ago
Craig Tiller	2794078c48	[transport] Split metadata_batch into its own target (#35496 ) (Required recursively splitting some other targets too) Gets us closer to eliminating `grpc_base`, and (more importantly) sets up some pieces of transport to be split out so I can rebuild them in coming months. Closes #35496 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/35496 from ctiller:chipchip `5319fb925d` PiperOrigin-RevId: 597304996	1 year ago
Craig Tiller	e58268525a	[chttp2] Reland: Fix bug in timeout encoding (#34812 )	1 year ago
Craig Tiller	af7aa3b127	Revert "[chttp2] Fix bug in timeout encoding" (#34811 ) Reverts grpc/grpc#34751	1 year ago
Craig Tiller	afe5f6d2a4	[chttp2] Fix bug in timeout encoding (#34751 ) Just the right combination of timeout values could lead to a large amount of growth in the timeout cache, leading to high memory usage and high cpu utilization on the client attempting that encoding. Fix: cap the number of cached timeout values we'll consider to a very small number (I'm choosing five). Add a fuzzer that ensures that we're actually respecting the limits of inaccuracy we're imposing upon ourselves. --------- Co-authored-by: ctiller <ctiller@users.noreply.github.com>	1 year ago
Craig Tiller	7c59c09f43	[chttp2] Bound write sizes based on observed write performance (#34665 ) Instead of fixing a target size for writes, try to adapt it a little to observed bandwidth. The initial algorithm tries to get large writes within 100-1000ms maximum delay - this range probably wants to be tuned, but let's see. The hope here is that on slow connections we can not back buffer so much and so when we need to send a ping-ack it's possible without great delay.	1 year ago