No it shouldn’t take much longer than a couple of minutes. For instance on my machine it only takes 2 minutes. There is definitely something wrong with your setup. In the log you posted, it shows that there are no requests outstanding in the queue, which is a clear sign that it’s not working as expected. I cannot help you more on this, unless you attach the exact commands you are running and their output log (in a text file, not an image) so I can figure out the problem.
Regards, Arash On 13 Apr 2016, at 19:19, Ata Fatahi baarzi <[email protected]<mailto:[email protected]>> wrote: Thank Arash, I run the first command and it did not end after about 10 hours! and after I myself end it by CTRL+C. Then I run second command and also it did not end after 14 hours! and it was generating output. finally, after 14 hours I end it by CTRL+C. The attached screenshot is 13th hour of running second command. what do you mean by "couple of minutes"? something more than 14 hours?! On Wed, Apr 13, 2016 at 8:58 PM, Arash Pourhabibi Zarandi <[email protected]<mailto:[email protected]>> wrote: Dear Ata, Both commands end after a couple of minutes. By the way, there is no need to run both. You should only use one of them. The first command creates the scaled dataset, and warms up the server at the same time. However, if you have already created the scaled dataset, you only need to execute the second command to warm up the server. Regards, Arash On 13 Apr 2016, at 09:25, Ata Fatahi baarzi <[email protected]<mailto:[email protected]>> wrote: HI, In Data Caching benchmark do the following commands end by themselves or I myself should end them by Ctrl+C ? ./loader -a ../twitter_dataset/twitter_dataset_unscaled -o ../twitter_dataset/twitter_dataset_30x -s docker_servers.txt -w 4 -S 30 -D 4096 -j -T 1 ./loader -a ../twitter_dataset/twitter_dataset_30x -s docker_servers.txt -w 4 -S 1 -D 4096 -j -T 1 -- Best Regards Ata Fatahi Baarzi<http://ce.sharif.edu/~fatahibarzi> -- Best Regards Ata Fatahi Baarzi<http://ce.sharif.edu/~fatahibarzi> <data_caching_output.PNG>
