Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-node heartbeat statistics #40

Closed
robgjansen opened this issue Feb 15, 2012 · 2 comments
Closed

Per-node heartbeat statistics #40

robgjansen opened this issue Feb 15, 2012 · 2 comments

Comments

Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@robgjansen
Copy link
Member

@robgjansen robgjansen commented Feb 15, 2012

Log a heartbeat every X seconds at log level Y with some aggregate statistics for each node:

  1. We currently take measurements whenever "processing" inside of a plug-in, and delay events for the associated node based on its CPU speed. We should also track the total measured processing time of each node, and log this information in the heartbeat message
  2. Similarly, track and report total bytes in/out of each node
  3. Approximate memory usage would be useful, which we could track as the sum of the registered memory as well as new heap allocations (by intercepting malloc family)

Add config options to XML that enables nodes to choose their own X and Y. Also include simulation-wide defaults for X and Y (editable on the command line) in case nodes do not choose to specify them.

@ghost ghost assigned robgjansen Feb 28, 2012
robgjansen added a commit that referenced this issue Feb 28, 2012
A new tracker class tracks node statistics. Currently, we are tracking
CPU processing times for each node application (time spent executing
inside the plug-in) and bytes in and out of each network interface. 

This also includes some code to track memory used by the plug-in, but
the malloc family of functions that we normally would intercept for this
feature are commented out due to initialization errors when preloading.

Takes care of 1, 2, and most of 3 in issue #40
@robgjansen
Copy link
Member Author

@robgjansen robgjansen commented Mar 27, 2012

PRELOADing malloc results in segfault before the program starts. Should we use malloc hooks instead?

http://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Hooks-for-Malloc.html

robgjansen added a commit that referenced this issue Jun 1, 2012
XML attributes 'heartbeatfrequency' and 'heartbeatloglevel' to the
node element may now be used to specify those options in the XML
simulation file. The default command line values are used for a node if
the attributes are not specified for that node.

refs #40
@robgjansen
Copy link
Member Author

@robgjansen robgjansen commented Aug 17, 2012

This was implemented in v1.5. Bugs should be files separately.

@robgjansen robgjansen closed this Aug 17, 2012
robgjansen pushed a commit that referenced this issue Jun 30, 2020
I *think* these are the last ones we need for phold: epoll, uname, and gethostname. We still need the shadow-side handlers for these, though.

Merged via pull request #40 from robgjansen/jnewsome/more-shim-wrappers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment