You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The memory consumption went 25 ~ 30MB per 50000 events when commented
CallStack(ba);
inbool 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.
The text was updated successfully, but these errors were encountered: