Created
March 25, 2011 16:06
-
-
Save goncalossilva/887095 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| rbx-head :037 > lb = Rubinius::Agent.loopback | |
| => #<Rubinius::Agent:0x1884 @decoder=#<BERT::Decode:0x1888 @in=#<IO:0x188c> @peeked=""> @io=#<IO:0x188c> @encoder=#<BERT::Encode:0x1894 @out=#<IO:0x188c>>> | |
| rbx-head :038 > lb.get("system.memory.counter.bytes").last # this is memory | |
| => 45022024 | |
| rbx-head :040 > lb.get("system.memory.counter.objects").last # this is the amount of object allocations | |
| => 1367753 | |
| rbx-head :041 > lb.get("system.gc.full.count").last + lb.get("system.gc.young.count").last # this is the amount of gc runs | |
| => 13 | |
| rbx-head :042 > lb.get("system.gc.full.wallclock").last + lb.get("system.gc.young.wallclock").last # and the amount of time spent gcing | |
| => 217 |
Yes, they are correct. The wallclock time is in milliseconds btw.
They are not yet documented, but I will make an effort to do so before the next release.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Are the assumptions above correct? I wonder if I can also use the loopback agent to get the time (process, wall and cpu).
Another question: is there any documentation on all the available parameters?