From 1cb21d9ccdfd14ba8ee2f3eac421b1ab1d8c802e Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Mon, 22 Oct 2007 20:01:57 +0000
Subject: [PATCH] edits

[Imported from Trac: page Performance, version 14]
---
 Performance.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Performance.md b/Performance.md
index 2575b0f..640f273 100644
--- a/Performance.md
+++ b/Performance.md
@@ -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