Project

General

Profile

Bug #41827

beast frontend reads body in small buffers

Added by Casey Bodley over 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
beast
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

the flat_buffer starts very small and rarely grew above 512 bytes when reading headers. this buffer's capacity() is what determines the size of reads when when recv_body() calls boost::beast::http::async_read_some(). raising this buffer size to a static 64k greatly reduces the number of socket reads


Related issues

Copied to rgw - Backport #41846: nautilus: beast frontend reads body in small buffers Resolved
Copied to rgw - Backport #41847: mimic: beast frontend reads body in small buffers Resolved
Copied to rgw - Backport #41848: luminous: beast frontend reads body in small buffers Rejected

History

#1 Updated by Casey Bodley over 4 years ago

  • Status changed from New to Pending Backport

#2 Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41846: nautilus: beast frontend reads body in small buffers added

#3 Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41847: mimic: beast frontend reads body in small buffers added

#4 Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41848: luminous: beast frontend reads body in small buffers added

#5 Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF