On Mon, 8 Apr 2024 22:41:04 +0900 Honggyu Kim <honggyu....@sk.com> wrote: [...] > To explain this, I better share more test results. In the section of > "Evaluation Workload", the test sequence can be summarized as follows. > > *. "Turn on DAMON." > 1. Allocate cold memory(mmap+memset) at DRAM node, then make the > process sleep. > 2. Launch redis-server and load prebaked snapshot image, dump.rdb. > (85GB consumed: 52GB for anon and 33GB for file cache) > 3. Run YCSB to make zipfian distribution of memory accesses to > redis-server, then measure execution time. > 4. Repeat 4 over 50 times to measure the average execution time for > each run.
Sorry, "Repeat 4 over 50 times" is incorrect. This should be "Repeat 3 over 50 times". > 5. Increase the cold memory size then repeat goes to 2. > > I didn't want to make the evaluation too long in the cover letter, but > I have also evaluated another senario, which lazyly enabled DAMON just > before YCSB run at step 4. I will call this test as "DAMON lazy". This > is missing part from the cover letter. > > 1. Allocate cold memory(mmap+memset) at DRAM node, then make the > process sleep. > 2. Launch redis-server and load prebaked snapshot image, dump.rdb. > (85GB consumed: 52GB for anon and 33GB for file cache) > *. "Turn on DAMON." > 4. Run YCSB to make zipfian distribution of memory accesses to > redis-server, then measure execution time. > 5. Repeat 4 over 50 times to measure the average execution time for > each run. > 6. Increase the cold memory size then repeat goes to 2. > > In the "DAMON lazy" senario, DAMON started monitoring late so the > initial redis-server placement is same as "default", but started to > demote cold data and promote redis data just before YCSB run. [...] Thanks, Honggyu
