tree be477e3f5f3886186aff7d183d21772beb8b607b
parent cf18c9e9d4d44f6671a3fe6011bb53d8ee9bd92b
author Bruce Merry <bmerry@ska.ac.za> 1593066621 +0200
committer GitHub <noreply@github.com> 1593066621 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJe9ER9CRBK7hj4Ov3rIwAAdHIIAEtHeo75BCdVhsCZPDcAtRqM
 f/hzn7h6zf3kevWSDHe31LN5k3ufVc4i91THdSOuuprjzOncBS0b2YrQcmKWJ2gJ
 omThTbxpsOoV1L5YbeeYhsjo6zrBM07i68Wj419o9MZnYOvU4upL5EzqDAvznce/
 yD2HhUQrd6m15wlzlnKuB42YjVkjx13fuDJN75b/FtYG+FgL4EsfsRSNRilegnBt
 t1rP7hnOHhIOWHBVliTyKICXFR9Y1u6tggA1tcQMREEXJwn6/17GF8ieyzTCo9/J
 9NQS15ZbkJxXD7XqLqLeJ38BjAPcmWgZRef7IX7OXofpdUemI/QaLHLCvZ0mApc=
 =b1pY
 -----END PGP SIGNATURE-----
 

bpo-41002: Optimize HTTPResponse.read with a given amount (GH-20943)


I've done the implementation for both non-chunked and chunked reads. I haven't benchmarked chunked reads because I don't currently have a convenient way to generate a high-bandwidth chunked stream, but I don't see any reason that it shouldn't enjoy the same benefits that the non-chunked case does. I've used the benchmark attached to the bpo bug to verify that performance now matches the unsized read case.

Automerge-Triggered-By: @methane