CGCL-codes / HME

HME a hybrid memory emulator for studying the performance and energy characteristics of upcoming NVM technologies. HME exploits features available in commodity NUMA architectures to emulate two kinds of memories: fast, local DRAM, and slower, remote NVM on other NUMA nodes. HME can emulates a wide range of NVM latencies and bandwidth by injecting different memory access delay on the remote NUMA nodes. To facilitate programmers and researchers in evaluating the impact of NVM on the application performance, a high-level programming interface is also provided to allocate memory from NVM or DRAM nodes.
48 stars 18 forks source link

Computer configuration #1

Open usergit19 opened 6 years ago

usergit19 commented 6 years ago

@Gumi-presentation-by-Dzh My computer configuration is Intel(R) Xeon(R) CPU E3-1245 v3 @ 3.40GHz, I'm working on a virtual machine ubuntu 16.04, and I can't run a program on HME successfully, is it due to the computer configuration ? it's mentionned that HME relies on a Xeon E5 / E7, that's mean that the CPUs should be a Xeon E5 / E7 ?

Gumi-presentation-by-Dzh commented 5 years ago

Sorry to answer later. Yes, accurately speaking, we built our emulator on Intel Ivy Bridge, Sandy Bridge and Haswell Micro-architecture which is commonly used in Xeon CPUs. Because our emulator based on PMU, so we need to bind a specific event mask to a specific PMU counter, but the PMU counter is different on each CPUs or Microarchitecture. Meanwhile, we did not specifically consider the use of the simulator in the virtualized environment, because we do not know whether the simulator can still read the value of the events on the PMU counter in the virtual machine. We especially doubt whether there is PMU counter in the virtual machine. We recommend that you run the virtual machine directly using the emulator so that the virtual machine will run directly in the emulation environment instead of opening the emulator inside the virtual machine.