Opened at 2014-12-04T00:23:44Z
Closed at 2020-10-30T12:35:44Z
#2348 closed enhancement (wontfix)
optimise concat function in cloud_common.py
| Reported by: | daira | Owned by: | daira |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.15.0 |
| Component: | code-storage | Version: | cloud-branch |
| Keywords: | cloud-backend performance easy | Cc: | |
| Launchpad Bug: |
Description
At https://github.com/LeastAuthority/tahoe-lafs/blob/cloud-rebased/src/allmydata/storage/backends/cloud/cloud_common.py#L419, the inner loop can be replaced with a slice assignment, which might be more efficient. This affects concatenation of chunks in the cloud backend.
Change History (5)
comment:1 Changed at 2014-12-04T00:23:58Z by daira
- Version changed from 1.10.0 to cloud-branch
comment:2 Changed at 2016-03-22T05:02:25Z by warner
- Milestone changed from 1.12.0 to 1.13.0
comment:3 Changed at 2016-06-28T18:17:14Z by warner
- Milestone changed from 1.13.0 to 1.14.0
renaming milestone
comment:4 Changed at 2020-06-30T14:45:46Z by exarkun
- Milestone changed from 1.14.0 to 1.15.0
Moving tickets out of closed milestones.
comment:5 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
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.
Milestone renamed