Changes between Initial Version and Version 1 of Ticket #1045


Ignore:
Timestamp:
2010-05-18T01:24:48Z (15 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1045

    • Property Keywords memory sftp added
    • Property Owner changed from nobody to somebody
    • Property Component changed from unknown to code
    • Property Milestone changed from 1.8.0 to undecided
  • Ticket #1045 – Description

    initial v1  
    11Today, I copied about 12'000 files for a total size of about 52 GB into Tahoe with the SFTP frontend.
    22
    3 Here's what {{{top}}} has to says about the Tahoe process after this operation.
     3Here's what {{{top}}} has to say about the Tahoe process after this operation.
    44{{{
    5  2765 francois  20   0 2059m 1.5g 2472 D    2 75.4 527:08.83 python                   
     5 2765 francois  20   0 2059m 1.5g 2472 D    2 75.4 527:08.83 python
    66}}}
    77
     
    1212Here is what Brian Warner proposed on IRC:
    1313
    14 {{{
    15 keep track of the process size vs time, with munin or a script that saves values and then graph them with gnuplot or something
    16 I think tahoe's /stats WAPI will give you process-memory-size info
    17 the idea is to do some operation repeatedly, measure process-space change while that's running, then switch to some other operation and measure that slope, and look for differences
    18 'cp' to an SFTP-mounted FUSEish thing, vs 'tahoe cp' might be a good comparison
    19 }}}
     14> keep track of the process size vs time, with munin or a script that saves values and then graph them with gnuplot or something
     15> I think tahoe's /stats WAPI will give you process-memory-size info
     16> the idea is to do some operation repeatedly, measure process-space change while that's running, then switch to some other operation and measure that slope, and look for differences
     17> 'cp' to an SFTP-mounted FUSEish thing, vs 'tahoe cp' might be a good comparison