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

Memory usage - different values reported by SwiftMetrics and Activity Monitor (macOS) #2

Closed
tobespc opened this issue Jan 26, 2017 · 5 comments
Labels

Comments

@tobespc
Copy link
Member

tobespc commented Jan 26, 2017

Raised from

https://github.com/IBM-Swift/SwiftMetrics/issues/50

@tobespc tobespc added the bug label Jan 26, 2017
@rolivieri
Copy link
Contributor

@hhellyer, @tobespc Thanks for the info. I added those additional columns and I see now that the value reported under "Real Memory" in Activity Monitor matches the value reported by SwiftMetrics. I am then assuming the intention is to report [via SwiftMetrics] the "Real Memory" value since it includes shared memory. Is this correct? I am guessing this is also what has been done for the other runtimes. If so, then it sounds like it is working as designed. Can you guys confirm?

@rolivieri
Copy link
Contributor

@TheSoundDefense - Keeping you in the loop; see above.

@tobespc
Copy link
Member Author

tobespc commented Jan 27, 2017

@rolivieri so that is then intention right now, however, if you would like the value to be sent without including shared memory we would require a larger change as we don't collect that right now. We can do it, it would just be put as a lower priority behind the rest of the work for swiftmetrics.

So, my question is how critical to you is have the memory value without including shared memory ?

@rolivieri
Copy link
Contributor

@tobespc As of now, I don't have a use case for collecting the value without shared memory. If we are taking for Swift the same approach that was taken for the other runtimes (node, java, etc.) then I'd say we are good for now.

@stalleyj
Copy link
Member

I'm going to close this issue as we are providing the same information across all runtimes. I've also raised an enhancement to implement the applicationPrivateSize on macOS #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants