Hi Marco, That command is used to quickly estimate the maximum throughput a server can achieve, just to give you a hint for tuning. No need to run it for a whole day. It is not important that the number is very precise. Pick any. You need to play with the load on the client (using "-r"), increasing it up to the point at which the response time starts shooting up but is still below the threshold of 5ms (you can use another threshold depending on the environment).
Regards, Djordje ________________________________________ From: Marco Guazzone [[email protected]] Sent: Saturday, November 16, 2013 8:32 AM To: [email protected] Subject: [datacaching] Max throughput rps Hello, As described in the DataCaching docs, I've run the command ./loader -a ../twitter_dataset/twitter_dataset_30x -s servers.txt -g 0.8 -T 1 -c 200 -w 8 to determine the maximum throughput "rps" This command is has been running for 1 day and continue to output lines like this one (but with different numbers each time): timeDiff, rps, requests, gets, sets, hits, misses, avg_lat, 90th, 95th, 99th, std, min, max, avgGetSize 1.000001, 48539.0, 48539, 38957, 9582, 38131, 826, 11746.735650, 13000.000000, 13000.000000, 13000.000000, 907.031451, 10428.917885, 12742.028236, 818.065996 Outstanding requests per worker: 293396 288454 206451 197955 172338 197496 261821 214019 count 0 count 0 count 0 Looking inside the loader.c I read that as default the program runs forever. So I understand the final "rps" value (i.e., the one I will use for running the benchmark) is the max value of the above "rps" columns I obtain as output from the loader, is it? If so, when is it "safe" to stop the execution of loader and get such value? If not so, can you help me to understand better. Thank you for the help Best, -- Marco
