in-line the Memory Page
[Imported from Trac: page Performance, version 15]
parent
1cb21d9ccd
commit
8da5d2a32c
|
@ -2,7 +2,21 @@ Some basic notes on performance:
|
||||||
|
|
||||||
## Memory Footprint
|
## Memory Footprint
|
||||||
|
|
||||||
[The [MemoryFootprint](MemoryFootprint) page](MemoryFootprint) has more specific information.
|
We try to keep the Tahoe memory footprint low by continuously monitoring the
|
||||||
|
memory consumed by common operations like upload and download.
|
||||||
|
|
||||||
|
For each currently active upload or download, we never handle more than a
|
||||||
|
single segment of data at a time. This serves to keep the data-driven
|
||||||
|
footprint down to something like 4MB or 5MB per active upload/download.
|
||||||
|
|
||||||
|
Some other notes on memory footprint:
|
||||||
|
|
||||||
|
* importing sqlite (for the share-lease database) raised the static
|
||||||
|
footprint by 6MB, going from 24.3MB to 31.5MB (as evidenced by the munin
|
||||||
|
graph from 2007-08-29 to 2007-09-02).
|
||||||
|
|
||||||
|
* importing nevow and twisted.web (for the web interface) raises the static
|
||||||
|
footprint by about 3MB (from 12.8MB to 15.7MB).
|
||||||
|
|
||||||
The
|
The
|
||||||
[32-bit memory usage graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats.html)
|
[32-bit memory usage graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats.html)
|
||||||
|
|
Loading…
Reference in a new issue