Opened at 2012-07-03T15:08:07Z
Closed at 2020-10-30T12:35:44Z
#1786 closed defect (wontfix)
cloud backend: limit memory usage
| Reported by: | davidsarah | Owned by: | davidsarah |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | code-storage | Version: | cloud-branch |
| Keywords: | memory large cloud-backend | Cc: | |
| Launchpad Bug: |
Description
The cloud backend at one point had a mechanism to limit the total amount of memory allocated for share chunks (providing backpressure to operations that would require more chunks), but I couldn't get that to work. Restore and fix it!
Change History (1)
comment:1 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.
If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).
If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.
Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.