[tahoe-lafs-trac-stream] [tahoe-lafs] #1523: MDMF upload via web-API uses much more memory in the gateway process than expected

[tahoe-lafs]

#1523: MDMF upload via web-API uses much more memory in the gateway process than
expected
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  davidsarah
  davidsarah             |     Status:  assigned
         Type:  defect   |  Milestone:  undecided
     Priority:  major    |    Version:  1.9.0a1
    Component:  code-    |   Keywords:  mdmf memory-leak tahoe-put
  frontend-web           |  performance
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Brian said on IRC that he didn't want to treat this as a blocker for v1.9.
 Presumably his reasoning is that it isn't a regression—nothing in MDMF can
 be a regression. :-) And also nothing in MDMF is turned on by default for
 v1.9. Still, this is pretty disappointing behavior. It means people cannot
 upload (put) MDMFs larger than their RAM (or actually than about 1/6 of
 their available RAM)? If we're going to ship v1.9 with this behavior, we
 certainly need to make sure [source:docs/performance.rst] tells about it!

 Brian also said that he thought fixing it would require a new method added
 to the API of
 [source:trunk/src/allmydata/interfaces.py?annotate=blame&rev=5212#L91
 RIStorageServer]. I can't imagine why that would be, but I'm way too
 sleepy at this point to think about such things.

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