#3872 closed defect (fixed)

Limit memory and CPU usage of writes/reads via HTTP storage server

Reported by: itamarst Owned by: GitHub <noreply@…>
Priority: normal Milestone: HTTP Storage Protocol
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description

Right now writing a very large chunk, reading a very large chunk, and perhaps other operations, can allocate unlimited memory or block the event loop for a long time. This should be fixed.

Change History (2)

comment:1 Changed at 2022-04-18T17:19:01Z by itamarst

Probably want a limited_content(request, max_length) utility function for the client, that errors out if it too much data is sent.

comment:2 Changed at 2022-07-15T16:44:12Z by GitHub <noreply@…>

  • Owner set to GitHub <noreply@…>
  • Resolution set to fixed
  • Status changed from new to closed

In 69f90e6/trunk:

Merge pull request #1203 from tahoe-lafs/3872-resource-limits-http-storage

A variety of CPU and memory resource limits for the HTTP storage client and server

Fixes ticket:3872

Note: See TracTickets for help on using tickets.