[tahoe-lafs-trac-stream] [tahoe-lafs] #1796: refuse to upload/download a mutable file if it cannot be done in the available memory

[tahoe-lafs]

#1796: refuse to upload/download a mutable file if it cannot be done in the
available memory
------------------------------+-------------------------------------------
     Reporter:  davidsarah    |      Owner:
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-mutable  |    Version:  1.9.2
   Resolution:                |   Keywords:  mutable large usability error
Launchpad Bug:                |
------------------------------+-------------------------------------------

Comment (by davidsarah):

 {{{
 (00:12:56) davidsarah: how to determine usable memory: free + buffers +
 cached as reported by the 'free' command?
 (00:13:21) davidsarah: (free physical + buffers + cached that is)
 (00:13:38) zooko: I don't think it is that simple.
 (00:13:41) zooko: I mean,
 (00:13:46) zooko: suppose that number comes out to 2 GB
 (00:13:51) davidsarah: ok
 (00:14:00) zooko: but if you then try to allocate 2 GB of RAM, you push
 something else into swap thrash.
 (00:14:02) zooko: For example.
 (00:14:17) davidsarah: right. but some swapping is fine, no?
 (00:14:26) davidsarah: we're trying to stop pathological swapping
 (00:14:29) zooko: Hm.
 (00:14:36) zooko: I don't know.
 (00:14:50) davidsarah: because the OS doesn't do a good job of stopping
 pathological swapping
 (00:14:51) zooko: I'm inclined to leave the handling of too-large SDMFs
 simple and dumb and bad...
 }}}

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1796#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage