[tahoe-lafs-trac-stream] [tahoe-lafs] #1513: memory usage in MDMF publish

[tahoe-lafs]

#1513: memory usage in MDMF publish
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:  1.9.0
    Component:  code-    |    Version:  1.9.0a1
  mutable                |   Keywords:  mutable mdmf memory-leak
   Resolution:           |  performance
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Let's call it a memory "leak" if doing some operation repeatedly results
 in progressively greater memory usage, such that if you do that operation
 enough times it will use up all the memory in your system. Let's not call
 it a memory "leak" if it uses up way too much RAM. Note that last time I
 heard, CPython never releases memory back to the operating system:
 http://www.evanjones.ca/memoryallocator/

 It sounds to me like there is a major problem here, which is that Tahoe-
 LAFS uses up way too much memory. I don't see evidence that there is a
 "leak" per se, and I don't consider it to be a major problem that CPython
 never releases memory back to the operating system.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1513#comment:4>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage