The number of events captured by ProcmonC is much smaller than that of ProcmonX · Issue #6 · zodiacon/ProcMonXv2 · GitHub
More Web Proxy on the site http://driver.im/
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
Hello, I found a problem. In your project, when all the basic event types (basic) are selected (9 categories in total), the events captured by ProcmonX are much larger than those of ProcmonC (console project) with the same configuration. This is very strange. I have made special research on this, but I haven't found any difference (they obviously use the same API).
On my device, when all basic event types are selected (9 categories in total):
ProcmonX can capture 9000 ~ 10000 events per second
ProcmonC can capture 4000 ~ 5000 events per second
PS:
I know that for some reason, two projects are not allowed to run at the same time. You can try to run them separately when testing.
I didn't set any filters.
This was discovered when I applied it to my project and I found that the value of the event counter was much smaller than what it showed in ProcmonX.
This is very strange.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Hello, I found a problem. In your project, when all the basic event types (basic) are selected (9 categories in total), the events captured by ProcmonX are much larger than those of ProcmonC (console project) with the same configuration. This is very strange. I have made special research on this, but I haven't found any difference (they obviously use the same API).
On my device, when all basic event types are selected (9 categories in total):
ProcmonX can capture 9000 ~ 10000 events per second
ProcmonC can capture 4000 ~ 5000 events per second
PS:
This was discovered when I applied it to my project and I found that the value of the event counter was much smaller than what it showed in ProcmonX.
This is very strange.
The text was updated successfully, but these errors were encountered: