add 64-bit memcheck graph
[Imported from Trac: page Performance, version 11]
parent
cf2f716086
commit
4ddc0ed4f9
|
@ -6,12 +6,19 @@ Some basic notes on performance:
|
||||||
|
|
||||||
The
|
The
|
||||||
[munin graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats.html)
|
[munin graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_memstats.html)
|
||||||
shows our static memory footprint (starting a node but not doing
|
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
|
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
|
node to about 29MB. (we only process one segment at a time, so peak memory
|
||||||
consumption occurs when the file is a few MB in size and does not grow beyond
|
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.
|
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.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
|
||||||
|
of reasons for it to be 2x, but the results show something closer to 6x.
|
||||||
|
|
||||||
## Network Speed
|
## Network Speed
|
||||||
|
|
||||||
### Test Results
|
### Test Results
|
||||||
|
|
Loading…
Reference in a new issue