[tahoe-lafs-trac-stream] [Tahoe-LAFS] #478: add memory-usage to stats-provider numbers

[Tahoe-LAFS]

#478: add memory-usage to stats-provider numbers
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:
         Type:           |     Status:  closed
  enhancement            |
     Priority:  major    |  Milestone:  undecided
    Component:  code-    |    Version:  1.1.0
  storage                |   Keywords:  performance memory statistics
   Resolution:  wontfix  |  privacy
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by exarkun):

 * status:  new => closed
 * resolution:   => wontfix


Old description:

> It would be nice for a Tahoe node to measure its own memory usage (when
> possible: i.e. under linux with a readable /proc/self/statm) and report
> them in the stats-provider data. This would also cause them to be logged
> to the foolscap logs each time the stats-gatherer asks for them.
>
> There is code to measure the memory usage in
> source:src/allmydata/test/check_memory.py

New description:

 It would be nice for a Tahoe node to measure its own memory usage (when
 possible: i.e. under linux with a readable /proc/self/statm) and report
 them in the stats-provider data. This would also cause them to be logged
 to the foolscap logs each time the stats-gatherer asks for them.

 There is code to measure the memory usage in
 source:src/allmydata/test/check_memory.py

--

Comment:

 It seems to me that measuring memory used by a process is something a
 third-party monitoring tool should do.  There's no need for every
 application to duplicate the functionality of discovering and then
 exposing this information.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/478#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage