-
Notifications
You must be signed in to change notification settings - Fork 28
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
LRB window tuning #10
Comments
Hi @lynnliu030 , Sorry for the late response. Your code runs correctly. I updated the doc and you can find the explanation of the output here: https://github.com/sunnyszy/lrb/blob/master/LRB_WINDOW_TUNING.md. I also updated the Github sample config. Here your current version would be slow because it only uses one concurrent process in simulating the 150 tasks sequentially. To make it faster, you can pull the latest Github version and I use GNU parallel to automatically config the amount of parallelism. You can also manually adjust the parallelism by changing the nodes in https://github.com/sunnyszy/lrb/blob/master/config/job_dev.yaml#L9 from |
@sunnyszy Sorry, but one more question, how long does it normally take for the simulation in the parallel mode? Say for the wiki-18 or -19 trace |
Hey @lynnliu030 , Each simulation is 20% of the time of the full trace. Depends on your # threads, you should be able to calculate the time. Also, when the algorithm decides to use smaller cache sizes to do linear fit, it needs additional rounds of simulations. |
@sunnyszy Thanks for the info! |
Hi, I was trying to tune the LRB window for a new trace, but I'm not sure whether I'm doing it correctly. I use the command below
And I got output in terminal as
And it just gets stuck there. I was wondering whether this gets running correctly? And how I am able to view the tuning result?
The text was updated successfully, but these errors were encountered: