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

Recording callstacks consumes too much memory #4

Open
hzqst opened this issue Apr 21, 2017 · 0 comments
Open

Recording callstacks consumes too much memory #4

hzqst opened this issue Apr 21, 2017 · 0 comments

Comments

@hzqst
Copy link
Owner

hzqst commented Apr 21, 2017

The memory consumption went 25 ~ 30MB per 50000 events when commented CallStack(ba); in bool CMonitorWorker::ParseMessage(PUCHAR data), while it went 50 ~ 60MB per 50000 events when CallStack is recorded.
It almost cost 150% memory than the event itself, since one event cost 100 bytes at average and the std::vector cost 24 + 8 * number of CCallStack which is commonly 10~15 = 144 bytes.
I am going to find a way to cut the std::vector's size down.
And is there anybody know how the Process Monitor saving all these events? it cost only 50MB with 500,000 events recorded.

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

No branches or pull requests

1 participant