#478 closed enhancement (wontfix)

add memory-usage to stats-provider numbers

Reported by: warner Owned by:
Priority: major Milestone: undecided
Component: code-storage Version: 1.1.0
Keywords: performance memory statistics privacy Cc:
Launchpad Bug:

Description (last modified by exarkun)

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

Change History (4)

comment:1 Changed at 2009-05-04T17:48:17Z by zooko

If you love this ticket (#478), then you might like tickets #54 (port memory usage tests to windows), #227 (our automated memory measurements might be measuring the wrong thing), #419 (pycryptopp uses up too much RAM), and #97 (reducing memory footprint in share reception

comment:2 Changed at 2009-12-04T05:00:58Z by davidsarah

  • Component changed from code-performance to code-storage
  • Keywords performance memory added

comment:3 Changed at 2009-12-13T05:11:36Z by davidsarah

  • Keywords statistics privacy added

comment:4 Changed at 2020-12-09T14:17:10Z by exarkun

  • Description modified (diff)
  • Resolution set to wontfix
  • Status changed from new to closed

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.

Note: See TracTickets for help on using tickets.