Hi Xiaodong, First off, thanks for your interest in CloudSuite. Your question is interesting indeed. The most realistic setup is having each of the tiers, assuming multi-tier benchmarks like in CloudSuite, in different physical machines. Therefore, I would suggest that each tier is run in a difference virtual machine instance. However, there are benchmarks that can rapidly saturate the network, becoming the first showstopper. An example of this is the Data Caching benchmark (i.e., Memcached). With a single 1Gbit NIC, I don’t think you can saturate the server. You could check if there are multiple network interfaces available per instance. You can assign a client per network interface. As an alternative, you could run all the tiers in the same instance, but this will not be very realistic.
Regards, Javier > On 06 Jul 2016, at 01:58, Xiaodong Wang <xw...@cornell.edu> wrote: > > Hi all, > > I'm a newbie to the cloud applications, and because it's pretty different > from the traditional desktop workloads such as SPEC, I'd like to make sure > that I have the correct setup. > > Because most of the Cloudsuite applications adopt a server-client model, It > seems that we need at least two machines, one running the server, and one > running the client. However, because I don't have 10Gbit ethernet support, > and the routing delay is beyond my control (running in AWS), is it acceptable > to run both client and server on the same CPU, for the purpose of > benchmarking? I can bind the client and server to different cores, but they > might interfere each other in hardware resources such as cache and memory > bandwidth. > > Please let me know what you think. Thank you very much for your help ! > > Best, > Xiaodong > > -- > Xiaodong Wang > > Computer Systems Laboratory > Cornell University > 356 Upson Hall > 607-379-5421 > xiaod...@csl.cornell.edu <mailto:xiaod...@csl.cornell.edu>
