Source.md

Run Migration

Start Source Redis-server

In source (netx7):

ps aux | grep redis # check existing redis-server
sudo kill -9 xxxx (redis pid)
cd ~; redis-server --protected-mode no --port 6380 --save "" --appendonly no &

Start Destination redis-server

In destination server (netx5):

ps aux | grep redis # check existing redis-server
sudo kill -9 xxxx (redis pid)
redis-server --protected-mode no --port 7380 --save "" --appendonly no&

Start destination priority pull

In destination server (netx5):

cd $NetMigrate/cpp/server/Source-protocol/
bash destination_migr.sh

In another terminal in destination server (netx5):

cd $NetMigrate/cpp/server/Source-protocol/server_agent/
bash start_dst_server_agent.sh

Start source migration script

In source server (netx7):

cd $NetMigrate/cpp/server/Source-protocol/
bash source_migr.sh

Run YCSB Clients Immediately

In client server (netx4):

cd $NetMigrate/cpp/YCSB-client
./ycsb-source -run -db KV -P workloads/workloadb  -P Source/run.properties -p threadcount=8 -s > ~/result/source-b-100.txt

After migration finishes, you will get the raw data output ~/result/source-b-100.txt in client server. You can draw throughput and latency figures from it using $NetMigrate/experiment_steps/figures/draw.py. The trend in the figures will be similar as the below examples.

cp ~/result/source-b-100.txt $NetMigrate/experiment_steps/figures/
cd $NetMigrate/experiment_steps/figures/
mkdir latency_fig
mkdir thorughput_fig
python3 draw.py source b 100

Throughput:

Median latency:

99%-tail latency:

Limit Source Redis CPU

If limiting source Redis CPU to mimic load-balancing scenario, e.g., 70% and 40% source redis CPU limit:

use this:

ps aux | grep redis
cpulimit -p 1234 -l 70

ps aux | grep redis
cpulimit -p 1234 -l 40