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