Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DRAMSim2-Gem5 Average Latency #59

Open
inciaf opened this issue Aug 17, 2016 · 2 comments
Open

DRAMSim2-Gem5 Average Latency #59

inciaf opened this issue Aug 17, 2016 · 2 comments

Comments

@inciaf
Copy link

inciaf commented Aug 17, 2016

Hi,

I am using your default ini files in my simulations (./DRAMSim -t traces/k6_aoe_02_short.trc -s system.ini.example -d ini/DDR3_micron_32M_8B_x8_sg15.ini -c 1000000). Average latency values are 280-300 ns. However, people use 50-100 ns as memory latency values in Gem5. It seems like my latency values are much higher than usual. I was wondering what the reason is for this difference between two latency values?

Thanks in advance,

Ahmet

@shavvn
Copy link
Collaborator

shavvn commented Sep 28, 2016

Hi Ahmet (@afinci),

We've moved DRAMSim2 to a new repo in https://github.com/umd-memsys. We will be providing support from there.

In answering your question, I think the reason is that k6_aoe_02_short.trc is only an example trace. The average latency depends heavily on your modeled system configurations and the work load (memory access patterns). In some system setup you could indeed get latency in the smaller range.

Best,
Shawn

@inciaf
Copy link
Author

inciaf commented Sep 28, 2016

Hi @shavvn ,

Thanks for your answer. Actually, I understood the problem and tried to solve it by writing a program called "remover.py". Basically, it randomly removes 'x' percentage of lines of the given memory trace to obtain a relatively less memory intensive trace. I posted it to the project's repo in case people may want to use it.

Thanks,

Ahmet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants