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
Originally posted by Soilorian July 16, 2024
Hello Mr. Sun, hope you are well
during my exploration on mgpu-sim and working with the mem.trace file I've noticed something strange. I was comparing the results of my analysis on this file and the pre made hit and miss count by using the -report-cache-hit-rate flag and I see some differences.
for example, on fir benchmark after building and running the code with the following command
./fir -timing -trace-mem -report-cache-hit-rate
there is a contradiction.
if we see the metrics file we see that for a specific cache like GPU[1].SA[3].L1SCache we see a total of 275 requests
but by simply counting the lines which match end.*GPU[1].SA[3].L1SCache regex pattern in the mem.trace file, we see a total of 320 matches
so either the metrics didn't catch all of the requests going to this cache or mem.trace file contains some redundant requests( I also checked, the requests didn't have the same id so they are not duplicate) what is the reason for this?
The text was updated successfully, but these errors were encountered:
Discussed in #84
Originally posted by Soilorian July 16, 2024
Hello Mr. Sun, hope you are well
during my exploration on mgpu-sim and working with the mem.trace file I've noticed something strange. I was comparing the results of my analysis on this file and the pre made hit and miss count by using the -report-cache-hit-rate flag and I see some differences.
for example, on fir benchmark after building and running the code with the following command
./fir -timing -trace-mem -report-cache-hit-rate
there is a contradiction.
if we see the metrics file we see that for a specific cache like GPU[1].SA[3].L1SCache we see a total of 275 requests
but by simply counting the lines which match end.*GPU[1].SA[3].L1SCache regex pattern in the mem.trace file, we see a total of 320 matches
so either the metrics didn't catch all of the requests going to this cache or mem.trace file contains some redundant requests( I also checked, the requests didn't have the same id so they are not duplicate) what is the reason for this?
The text was updated successfully, but these errors were encountered: