[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:  davidsarah      |      Owner:  davidsarah
         Type:  defect          |     Status:  assigned
     Priority:  major           |  Milestone:  undecided
    Component:  code-frontend-  |    Version:  1.9.0a1
  web                           |   Keywords:  memory tahoe-put performance
   Resolution:                  |
Launchpad Bug:                  |
--------------------------------+------------------------------------------

Comment (by davidsarah):

 When uploading an immutable file using {{{bin/tahoe put zeros}}} (again
 after restarting the nodes), the memory usage did not increase above:
 {{{
   PID   RSS    VSZ S TTY          TIME COMMAND
  1073 39776 163820 S ?        00:00:00 [...]/tahoe start
 ../grid/introducer
  1088 40784 124072 S ?        00:00:04 [...]/tahoe start ../grid/server1
  1098 41840 125264 S ?        00:00:04 [...]/tahoe start ../grid/server2
  1108 40940 124396 S ?        00:00:04 [...]/tahoe start ../grid/server3
  1118 40928 124532 S ?        00:00:09 [...]/tahoe start ../grid/server4
  1129 47900 175688 S ?        00:00:56 [...]/tahoe start
 }}}

 (I tried again using data from {{{/dev/urandom}}} in case of some
 optimization involving zero memory pages, with the same results.)

 I don't understand how the gateway avoided holding the file in memory. Did
 somebody fix #320 while I wasn't looking? :-)

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