search

1a1a11a / libCacheSim

a high performance library for building cache simulators
GNU General Public License v3.0
155 stars 33 forks source link

Cloudphysic block trace origin format #54

Closed haomactracy closed 7 months ago

haomactracy commented 7 months ago

Hi，can you provide Cloudphysic block trace origin format, i want to analyze it, but i cannot find the way to download a Cloudphsic block trace with offset and length. Thank you so much!

1a1a11a commented 7 months ago

Hi @haomactracy, you can download them here https://ftp.pdl.cmu.edu/pub/datasets/twemcacheWorkload/.cphy/

1a1a11a commented 7 months ago

Hi @haomactracy , since you study the offset and length, there is another dataset from Meta that you might be interested https://cachelib.org/docs/Cache_Library_User_Guides/Cachebench_FB_HW_eval/#list-of-traces

haomactracy commented 7 months ago

Thank you so much，i download the trace with vscsitrace Binary file，can you give me some information about how to get the offset and length from the trace？Thanks

1a1a11a commented 7 months ago

libCacheSim does not have the tool to print it, but take a look at vscsi.c and https://man.openbsd.org/vscsi.4

haomactracy commented 7 months ago

Thanks，but i have one question，that is，when i find the data structure of vscsi and print the trace(length and offset), typedef struct { uint32_t sn; uint32_t len; uint32_t nSG; uint16_t cmd; uint16_t ver; uint64_t lbn; uint64_t ts; } trace_v1_record_t; which element represents read or write i found that the simulator do not use the op(w or r), thanks for explaination!