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

better document LSM parameterization (Imported #146) #146

Open
nmcglo opened this issue Jun 14, 2016 · 0 comments
Open

better document LSM parameterization (Imported #146) #146

nmcglo opened this issue Jun 14, 2016 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@nmcglo
Copy link
Member

nmcglo commented Jun 14, 2016

Original Issue Author: Jonathan Jenkins
Original Issue ID: 146
Original Issue URL: https://xgitlab.cels.anl.gov/codes/codes/issues/146


We say to use fio, but don't have more specifics than that.

Some notes from Kevin:

“We measured I/O performance for 60 seconds at each access size as the access size was varied from 4 KiB to 8 MiB for each of sequential read, sequen- tial write, random read, and random write access patterns. The libaio engine was used in all cases with an iodepth of 4 and direct I/O. We set the model’s rate parameter to the maximum rate achieved by the sequential read and sequential write measurements. The overhead parameter was set to the median completion latency minus the transfer rate for the 4K request size. The seek parameters were set to the difference between the sequential and random latency values divided by the iodepth (4) at each request size.”

In fio, one of the output timings is “clat” or completion latency. So you take the optimal read or write transfer rate and compute a time to transfer 4K based on that, then subtract it from the clat value. That became our overhead parameter.

Overhead = clat - (4K/best_transfer_rate)

@nmcglo nmcglo added the documentation Improvements or additions to documentation label Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant