summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-01-05 20:41:42 +0000
committerGravatar admin <admin@branchable.com>2014-01-05 20:41:42 +0000
commit226fa90657a21703c70ee679b1b2a37502438514 (patch)
tree602661515faa5bb8400f3831c2981204c1cc2c98
parent93f718deaa640ab55ccd5cf33b40f6227fd59be0 (diff)
Added a comment
-rw-r--r--doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment b/doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment
new file mode 100644
index 000000000..6d03b4cdb
--- /dev/null
+++ b/doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.35"
+ subject="comment 3"
+ date="2014-01-05T20:41:35Z"
+ content="""
+Well, EKG either cannot see the leak, or perhaps haskell profiling generally cannot see it. Don't have a lot of experience with EKG, it's just a lot easier to ask for than full ghc profiling data..
+
+It's certainly useful information that you are constantly changing the files.
+
+I have tried to replicate this setup, with a few hundred files, and writing random stuff to them repeatedly. The RSS did not grow at all despite repeatedly changing and committing the files.
+
+I then tried adding a remote for it to sync with, and see evidence of a small leak there -- around 8 bytes per file transferred. The leak appears to be in the transfer code, not the git sync code; it happens with both git remotes and with directory special remotes.
+
+"""]]