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
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
The event currently sends the module count, time elapsed, and memory usage at the completion. However, the module count and time elapsed are on the analysis session, while memory usage is just overall. This means it's impossible to figure out a number like "this much memory per module on average", as a small session with only a few modules analyzed will still report the total usage.
Adding the RDT count will give a cumulative measure of what all is supposed to be there so we can do a generic count.
The text was updated successfully, but these errors were encountered:
The event currently sends the module count, time elapsed, and memory usage at the completion. However, the module count and time elapsed are on the analysis session, while memory usage is just overall. This means it's impossible to figure out a number like "this much memory per module on average", as a small session with only a few modules analyzed will still report the total usage.
Adding the RDT count will give a cumulative measure of what all is supposed to be there so we can do a generic count.
The text was updated successfully, but these errors were encountered: