add memory-usage to stats-provider numbers #478

New Issue

warner · 2008-06-24T01:47:38Z

warner commented

2008-06-24 01:47:38 +00:00

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

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

warner added the

major

enhancement

1.1.0

labels 2008-06-24 01:47:38 +00:00

warner added this to the undecided milestone 2008-06-24 01:47:38 +00:00

zooko commented

2009-05-04 17:48:17 +00:00

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

tahoe-lafs added the

code-storage

label 2009-12-04 05:00:58 +00:00

exarkun commented

2020-12-09 14:17:10 +00:00

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.

exarkun added the

wontfix

label 2020-12-09 14:17:10 +00:00

exarkun closed this issue

2020-12-09 14:17:10 +00:00

Sign in to join this conversation.