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 has been archived by the owner on Nov 17, 2023. It is now read-only.
When call profiler.dumps(), operators' call count is 2x the actual value.
This is because in ProfileOperator class in profiler.h, we are profiling a single operator call both as operator and as task (i.e. generating two events in the dump file for each operator call). However, in AggregateStats, we are simply mapping operator names to its stats. We should be a duplication check somewhere.
The text was updated successfully, but these errors were encountered:
Hey, this is the MXNet Label Bot.
Thank you for submitting the issue! I will try and suggest some labels so that the appropriate MXNet community members can help resolve it.
Here are my recommended labels: Feature
When call profiler.dumps(), operators' call count is 2x the actual value.
This is because in ProfileOperator class in profiler.h, we are profiling a single operator call both as operator and as task (i.e. generating two events in the dump file for each operator call). However, in AggregateStats, we are simply mapping operator names to its stats. We should be a duplication check somewhere.
The text was updated successfully, but these errors were encountered: