aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteve Slaven <bpk@hoopajoo.net>2009-08-07 22:40:10 (GMT)
committerSteve Slaven <bpk@hoopajoo.net>2009-08-07 22:40:10 (GMT)
commitbc30ead661de95b2bba2a6e0f0187ff84e1af06a (patch)
treea1b1f571c58fbb9c872d52a1afdb42519ae95b7f
parentce1fe76c76f1a6ab0c7f7e1080afd88f4fe969f6 (diff)
downloadfusearchive-bc30ead661de95b2bba2a6e0f0187ff84e1af06a.zip
fusearchive-bc30ead661de95b2bba2a6e0f0187ff84e1af06a.tar.gz
fusearchive-bc30ead661de95b2bba2a6e0f0187ff84e1af06a.tar.bz2
More notes about profiling
-rw-r--r--README5
1 files changed, 5 insertions, 0 deletions
diff --git a/README b/README
index 1bfe898..6aeda65 100644
--- a/README
+++ b/README
@@ -72,3 +72,8 @@ Other thoughts:
few ints and a block list even though it is very convenient
- Because of the way we refcount blocks I don't think we can open/unlink a
file like you would for temp files, but that's not the purpose anyway
+- Do some profiling using a loopback filesystem, since most of it will be
+ in memory we can see where the "real" bottlenecks are in the code by
+ taking out the disk access unknowns
+- ext3 uses a lot of space because of directory inodes reducing the savings
+ quite a bit