edits
[Imported from Trac: page Performance, version 14]
parent
49c3073b3f
commit
1cb21d9ccd
|
@ -5,7 +5,7 @@ Some basic notes on performance:
|
|||
[The [MemoryFootprint](MemoryFootprint) page](MemoryFootprint) has more specific information.
|
||||
|
||||
The
|
||||
[munin 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)
|
||||
shows our static memory footprint on a 32bit machine (starting a node but not doing
|
||||
anything with it) to be about 24MB. Uploading one file at a time gets the
|
||||
node to about 29MB. (we only process one segment at a time, so peak memory
|
||||
|
@ -13,7 +13,7 @@ consumption occurs when the file is a few MB in size and does not grow beyond
|
|||
that). Uploading multiple files at once would increase this.
|
||||
|
||||
We also have a
|
||||
[64-bit graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats_64.html), which currently shows a disturbingly large static footprint.
|
||||
[64-bit memory usage graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats_64.html), which currently shows a disturbingly large static footprint.
|
||||
We've determined that simply importing a few of our support libraries (such
|
||||
as Twisted) results in most of this expansion, before the node is ever even
|
||||
started. The cause for this is still being investigated: we can think of plenty
|
||||
|
|
Loading…
Reference in a new issue