Thank you for providing such a useful tool. I was confused about the output about DRAM energy in timeloop-mapper.stats.txt when using timeloop to analyze a three-level storage hierarchy (DRAM, Global Buffer and register file).
The energy for DRAM updates, writes, and reads listed in the ERT is 512, and the DRAM vector access energy listed in the SPECS section in timeloop-mapper.stats.txt is also 512. However, the per-scalar-access energy for DRAM used in the calculations in the STATS section of the output file is 64. Why are these three energy values inconsistent? The type of DRAM is LPDDR4.
Hi,
Thank you for providing such a useful tool. I was confused about the output about DRAM energy in
timeloop-mapper.stats.txt
when using timeloop to analyze a three-level storage hierarchy (DRAM, Global Buffer and register file).The energy for DRAM updates, writes, and reads listed in the ERT is
512
, and the DRAMvector access energy
listed in theSPECS
section intimeloop-mapper.stats.txt
is also512
. However, theper-scalar-access energy
for DRAM used in the calculations in theSTATS
section of the output file is64
. Why are these three energy values inconsistent? The type of DRAM isLPDDR4
.Here is ERT for DRAM:
Here is
SPEC
part andSTATS
part intimeloop-mapper.stats.txt