| 1 | | We try to keep the Tahoe memory footprint low by continuously monitoring the |
| 2 | | memory consumed by common operations like upload and download. |
| 3 | | |
| 4 | | For each currently active upload or download, we never handle more than a |
| 5 | | single segment of data at a time. This serves to keep the data-driven |
| 6 | | footprint down to something like 4MB or 5MB per active upload/download. |
| 7 | | |
| 8 | | Some other notes on memory footprint: |
| 9 | | |
| 10 | | * importing sqlite (for the share-lease database) raised the static |
| 11 | | footprint by 6MB, going from 24.3MB to 31.5MB (as evidenced by the munin |
| 12 | | graph from 8/29/07 to 9/2/07). |
| 13 | | |
| 14 | | * importing nevow and twisted.web (for the web interface) raises the static |
| 15 | | footprint by about 3MB (from 12.8MB to 15.7MB). |
| | 1 | The content from this page has been moved to [wiki:Performance the Performance page]. |
