1 \documentclass[12pt,a4paper]{journal}
2 \usepackage[utf8]{inputenc}
8 %\title{Reviewers' comments}
10 \newcommand{\AG}[2][inline]{%
11 \todo[color=green!50,#1]{\sffamily\textbf{AG:} #2}\xspace}
12 \newcommand{\JC}[2][inline]{%
13 \todo[color=red!10,#1]{\sffamily\textbf{JC:} #2}\xspace}
15 \newcommand{\Xsub}[2]{{\ensuremath{#1_\mathit{#2}}}}
17 %% used to put some subscripts lower, and make them more legible
18 \newcommand{\fxheight}[1]{\ifx#1\relax\relax\else\rule{0pt}{1.52ex}#1\fi}
20 \newcommand{\CL}{\Xsub{C}{L}}
21 \newcommand{\Dist}{\mathit{Dist}}
22 \newcommand{\EdNew}{\Xsub{E}{dNew}}
23 \newcommand{\Eind}{\Xsub{E}{ind}}
24 \newcommand{\Enorm}{\Xsub{E}{Norm}}
25 \newcommand{\Eoriginal}{\Xsub{E}{Original}}
26 \newcommand{\Ereduced}{\Xsub{E}{Reduced}}
27 \newcommand{\Es}{\Xsub{E}{S}}
28 \newcommand{\Fdiff}[1][]{\Xsub{F}{diff}_{\!#1}}
29 \newcommand{\Fmax}[1][]{\Xsub{F}{max}_{\fxheight{#1}}}
30 \newcommand{\Fnew}{\Xsub{F}{new}}
31 \newcommand{\Ileak}{\Xsub{I}{leak}}
32 \newcommand{\Kdesign}{\Xsub{K}{design}}
33 \newcommand{\MaxDist}{\mathit{Max}\Dist}
34 \newcommand{\MinTcm}{\mathit{Min}\Tcm}
35 \newcommand{\Ntrans}{\Xsub{N}{trans}}
36 \newcommand{\Pd}[1][]{\Xsub{P}{d}_{\fxheight{#1}}}
37 \newcommand{\PdNew}{\Xsub{P}{dNew}}
38 \newcommand{\PdOld}{\Xsub{P}{dOld}}
39 \newcommand{\Pnorm}{\Xsub{P}{Norm}}
40 \newcommand{\Ps}[1][]{\Xsub{P}{s}_{\fxheight{#1}}}
41 \newcommand{\Scp}[1][]{\Xsub{S}{cp}_{#1}}
42 \newcommand{\Sopt}[1][]{\Xsub{S}{opt}_{#1}}
43 \newcommand{\Tcm}[1][]{\Xsub{T}{cm}_{\fxheight{#1}}}
44 \newcommand{\Tcp}[1][]{\Xsub{T}{cp}_{#1}}
45 \newcommand{\Pmax}[1][]{\Xsub{P}{max}_{\fxheight{#1}}}
46 \newcommand{\Pidle}[1][]{\Xsub{P}{idle}_{\fxheight{#1}}}
47 \newcommand{\TcpOld}[1][]{\Xsub{T}{cpOld}_{#1}}
48 \newcommand{\Tnew}{\Xsub{T}{New}}
49 \newcommand{\Told}{\Xsub{T}{Old}}
55 \title{Answers to the questions of the reviewers}
57 \section{Questions and remarks of the first reviewer}
63 \item In Sec. 5, I found intriguing the fact of executing Algorithm 1 only
64 after the first iteration. I agree with you that your model finds the
65 best trade-off given some data, but what about the variability? We
66 know computer systems today always show some variability. You are
67 measuring the computation time and energy consumption for one
68 iteration only. Let's suppose something went bad in this first
69 iteration. The scaling factors will not be the best tradeoff because
70 variability has been ignored. What would be the solution for that?
71 Consider variability in the model.
73 \textbf{Answer:} In this paper we have considered that the application executes regular iterations over stable computers computing only this application. Therefore, we have assumed that the execution times of all the iterations of the application executed on the same computing node should be almost the same. For this reason we did not take into consideration the variability of the computer system. Moreover, applying the frequency scaling algorithm after many iterations would reduce its impact on the energy consumption especially for applications executing a relatively low number of iterations.
75 However, the variability of the computing system can be taken into consideration in a future work. For example, the proposed algorithm can be executed twice: after the first iteration the frequencies are scaled down according to the execution times measured in the first iteration, then after a fixed number of iterations, the frequencies are adjusted according to the execution times measured during the fixed number of iterations. If the computing power of the system is constantly changing, it would be interesting to implement a mechanism that detects this change and adjusts the frequencies according to the variability of the system.
77 Taking account of the variability of the system has been added as a perspective at the end of the paper.
80 \item Another point is that you mention
81 in the abstract and introduction that your solution has low overhead,
82 but it is a centralized solution. Probably it won't scale when we
83 reach hundreds or thousands of computer nodes: take one of that large
84 machines for example. In this paper experiments, only 16 and 32 nodes
88 We agree with the reviewer that the algorithm is centralized and might be a bottleneck if it was applied to an application running on many thousands of nodes. However, up to 144 nodes in a heterogeneous cluster, the overhead of the algorithm was very small, 0.15 ms, as presented in the simulation results of [6]. We did not execute experiments with more than 32 nodes on Grid'5000 because it does not have many nodes that allow DVFS operations and have energy measurement tools.
90 On the other hand, the scalability of the proposed algorithm can be improved if we use asynchronous computations or if the algorithm was distributed in a hierarchical manner where a leader is chosen for each cluster or a group of nodes to compute their scaled frequencies. Improving the scalability of the algorithm is beyond the scope of this paper.
94 \item In Fig 6, you draw lines between the points. Lines here mean nothing
95 since you are changing the benchmark. I would replot using for
96 instance a non-stacked bar plot with four colors (one site/16, one
97 site/32, two sites/16, two sites/32). I believe it would be much
98 easier to compare and avoid the problem of lines.
100 \textbf{Answer:} We agree with the reviewer. The curves in Figures 6 and 8 in the paper were replaced by histograms.
105 \item About the discussion of results shown in Fig 7, one consideration
106 draws my attention: "(...) the increase in the number of computing
107 nodes can increase the communication times and thus produces less
108 energy saving depending on the benchmarks being executed.". I agree
109 with you that for very large applications, synchronous collective
110 operations are very costly (take a very simple MPI-Allgather for
111 instance). You say that on scale this would produce less energy
112 savings, but your arguments for providing a solution for this was
113 based that today's supercomputers are achieving massive scale.
115 \textbf{Answer:} In Figure 7, the energy consumption of the benchmarks solving the class D and running on many scenarios are presented. The number of used nodes varies between 16 and 32 in the scenarios while the size of the problem is not modified. Therefore, the computations to communications times ratio is lower when 32 nodes are used instead of 16. When this ratio is small, it means there are not enough computations when compared to the communications times and the impact of scaling down the frequency of the CPU on its energy consumption is reduced. To solve this problem, the problem
116 should be solved on a number of nodes adequate to its size. For example, for the NAS benchmarks, the class E should have been solved on 32 nodes to have a good computations to communications times ratio.
119 \item In Sec 6.3, why did you choose to keep 32 processes for the evaluation
120 with multi-core clusters? How did you configure MPI for the results
122 \textbf{Answer:} In section 6.3, we wanted to evaluate how much energy can be saved when applying the proposed algorithm to message passing applications with iterations running over a grid composed of multi-core nodes. Therefore, the same experiments as in section 6.2 were conducted on the new multi-core platform. Instead of running one process per node as in the previous section, 3 or 4 processes were executed on each multi-core node. The total number of processes, 32 processes, was not modified in order to fairly compare the single core and the multi-core versions.
124 Only the architecture file was modified between the single and the multi-core architectures. For the single core architecture, the architecture file contains the name of 32 different nodes. For the multi-core architecture, the architecture file contains less nodes and for every node 3 or 4 slots (cores) are used. The total number of slots is equal to 32.
128 \item shown in Fig 8a? Some MPI implementations have an option to use shared
129 memory when processes share the same processor. I agree with you in
130 the explanation of the network card utilization, but this
131 shared-memory optimization is possible (sometimes automatically
132 detected by MPI if you pin processes to cores).
134 \textbf{Answer:} We did not manually pin processes to cores. Since the communication times
135 increased, we think that the shared memory was not used when two processes, running on the same node, exchange data.
137 \item In P33, Sec 6.5, you mention that the proposed algorithm outperforms
138 EDP because the former considers both metrics (time, energy) and the
139 same time. EDP does also, but using a single metric which you have
140 defined: energy x execution time. I think this is only a matter of
143 \textbf{Answer:} We agree with the reviewer, EDP also uses two metrics in the objective function: energy and delay. The sentence in the paper was modified to clarify this misunderstanding. The main difference between our algorithm and the EDP method is the used objective function. For EDP, the product of energy and delay must be minimized, while for our algorithm, the difference between the normalized performance and the normalized energy should be maximized. This new formulation of the objective function allows our algorithm to select the set of frequencies that gives the best tradeoff between the energy consumption and the performance. The objective function of EDP does not give the same frequencies as our algorithm and thus it is outperformed by our method. The results of the experiments confirm that the objective function used by our algorithm is more efficient than the one used by EDP.
146 \item Other complementary points to consider:
148 + P2, L51: there are three dots that looks like an error.
150 + P4, L36: also unusual three dots at the end of paragraph.
152 + P14 also has three dots in phrase endings. I consider this bad writing style.
154 + Fig 2b is missing the X scale ticks. You could show some examples of vectors.
156 + P23: "static power is assumed to be equal to 20\% of dynamic". Provide citation.
158 + Fig 6 is referenced in P23, but appears only in P25. Hard to read.
162 \textbf{Answer:} Answer: We have taken in consideration all these remarks and the paper was modified accordingly.
164 \item From the design of experiments, did you consider using replications?
165 There is no variability metric in your results. Have you run multiple
166 times and got the average (execution time and energy consumption)? I
167 feel that such variability needs to be accounted for, otherwise it is
168 very hard to affirm anything about measurements.
170 \textbf{Answer:} Each experiment has been executed many times and the results presented in the
171 figures are the average values of many executions. Since we have deployed the same operating system on the booked machines and we were the only users executing processes on them during the experiments, no significant variability in the execution time of the applications was noticed.
174 \item In summary, I think this is a very interesting work but the experimental evaluation lacks variability measurements, consider larger experiments (1K nodes for instance) to see how everything scales, and there is no overhead measurements although authors stress that in abstract/introduction.
176 \textbf{Answer:} For the time being, we do not have the resources nor the time to evaluate the proposed algorithm over large platforms composed of more than 1K nodes. However, as said in the perspectives of the paper, the evaluation of the scalability of the algorithm will be in a conducted in a future work as soon as we have access to larger resources. We have discussed the overhead of the algorithm and its complexity in section 6.5 and given in the answer to question 2 some solutions to improve its scalability and reduce its overhead.
178 For the variability issue, please refer to the answer to question 1.
184 \section{Questions and remarks of the second reviewer}
187 \item Move the contributions from related work to introduction
189 \item why emphasize it is a grid platform? the presentation of related work follows the logic of heterogeneous CPUs. Grid is only a type of platform with heterogeneous CPUs
191 \textbf{Answer:} We agree with the reviewer that a grid is a type of heterogeneous architecture and the proposed algorithm can also work on any heterogeneous architecture.
193 In \cite{4}, we have proposed a frequency selection algorithm for distributed applications running on heterogeneous clusters, while in this work, the proposed algorithm was adapted to the grid architecture which is composed
194 of homogeneous clusters interconnected by a wide area network which is slower than the local
195 network in each cluster.
197 \item Define what iterative message passing applications are and give exemplar applications of them targeted by this method.
199 \textbf{Answer:} In order to clarify things, we have replaced in the paper the sentence ``the iterative message passing applications'' with ``the message passing applications with iterations''. Therefore, the proposed algorithm can be applied to any application that executes the same block of instructions many times and it is not limited to iterative methods that repeat the same block of instructions until convergence.
201 Many problems are solved by methods with iterations such as solving a linear system of equations with Jacobi and Gauss-Seidel methods, Image processing with methods that apply the same instructions for each pixel or block of pixels, etc.
204 \item Figure 1 is not clearly explained. Where is the slack time in figure 1 and why slack time =0 for task 1?
207 \textbf{Answer:} Figure 1 was redrawn, the white space before the barrier is the slack time. Slack times occur when a node has to wait for another node to finish its computation to synchronously communicate with it. In Figure 1, task 1 was assumed to be the slowest task. All the other tasks will finish their computations before the slowest task and wait until it finishes its computation before being able to synchronously communicate with it. This waiting time is the slack time and since the slowest task do not have to wait for the other tasks it has almost no slack time.
209 \item define the parameters in eq. 1.
211 \textbf{Answer:} Fmax and Fnew have been defined as follows in the paper: ``$\Fmax$ is the maximum frequency before applying any DVFS and $\Fnew$ is the new frequency after applying DVFS''.
213 \item eq. 2: are you assuming each cluster has the same number of nodes?
215 \textbf{Answer:} No, each cluster can have a different number of nodes. Therefore, in the paper, $M$, the number of nodes in a cluster, was replaced by $M_i$, the number of nodes in cluster $i$, in all the equations.
217 \item Eq.2 implicitly assumes that there is no overlapping between computation and communication. Is it reasonable?
219 \textbf{Answer:} In this paper, only message passing applications with synchronous and blocking communications were considered. In such applications, there is no overlapping between computations and communications on a node.
221 Asynchronous applications are beyond the scope of this paper and will be considered in a future work.
223 \item eq. 2 is not clear:
225 -how to define and determine the slowest cluster h? the one before scaling or after scaling?
227 \textcolor{blue}{Answer: The slower task is the task which gives maximum execution time before scaling the frequency of the node. We have added this sentence to the paper (page 8).}
230 - what is the communication time without slack time
232 \textcolor{blue}{Answer: There is no synchronous communications with zero slack times, but if a node send a message to another node which is already waiting for that message. The latter will acknowledge the reception of the message from the sender without any delay. On the other hand, if the receiving node is still computing the sender has to wait for it to finish its computation to acknowledge the reception of the message. This time is called the slack time. }
235 - in equation, min operation is used to get the communication time, but in text, it says to use the slowest communication time, which should use the max operation then.
237 \textcolor{blue}{Answer: We agree with the reviewer and the sentence "slower communication time" changed to "communication time of the slower node" in the paper.}
239 \item discuss the difference between eq. 2 and the prediction model in references [5] and [6]
241 \textcolor{blue}{Answer: The prediction models in [5] and [6] are for homogeneous and heterogeneous clusters respectively, while eq. 2 is for a grid. where the homogeneous cluster predication model was used one scaling factor denoted as $S$, because all the nodes in the cluster have the same computing powers. Whereas, in heterogeneous cluster prediction model all the nodes have different scales and the scaling factors have denoted as one dimensional vector $(S_1, S_2, \dots, S_N)$. The execution time prediction model for a grid Equation (2) defines a two dimensional array of scales
242 $(S_{11}, S_{12},\dots, S_{NM_i})$. We have added this to the paper (page 8).}
244 \item Eq. 10: Can the authors comment on the energy consumed by communications?
246 \textcolor{blue}{Answer: The CPU during communications consumed only the static power power. While
247 in computations the CPU consumes both the dynamic and static communication, refer to \cite{3}. We have added this sentience to the paper, page 11.}
249 \item This work assume homogeneous cpu in one cluster. Line 55 says: even if the distributed message
250 passing iterative application is load balanced, the computation time of each cpu j in cluster i may be different Why?
252 \textcolor{blue}{Answer: The computation times may be slightly different due to the delay caused
253 by the scheduler of the operating system. We have added this in the paper.}
255 \item Comment why the applications in NAS parallel benchmark are iterative application? These applications are normally run in one cluster. Describe in more detail how they are run across multiple clusters.
257 \textcolor{blue}{Answer: The applications in NAS parallel benchmark are application with iterations because they iterate the same block of instructions (communications and computations) many times. All the benchmarks are MPI programs that allowed to be executed on any distributed memory platform such as clusters and grids with no required modifications. Since, we have deployed the same operating system on all the nodes, we just compile the source on one cluster and then copied the executable program on all the clusters. }
259 \item broken sentence in line 28 on page 12
261 \textcolor{blue}{Answer: The word "were" replaced with "where".}
263 \item Why $T_{old}$ is computed using eq. 12, which applies MAX over computation time and communication time, while in $T_{new}$, max and min operations are applied over computation and communication separately?
265 \textcolor{blue}{Answer: We agree with the reviewer, $T_{old}$ is the maximum execution time of the application before scaling the frequency and it is computed as in $T_{new}$ equation without scaling factors. So, we have changed the $T_{old}$ in the paper as as follows:
268 T_{old} = \mathop{\max_{i=1,2,\dots,N}}_{j=1,2,\dots,M_i} (\Tcp[ij]) +
269 \mathop{\min_{i=1,2,\dots,N}} (\Tcm[hj] )
273 \item Line 55 on page 16 is to define the slack time, which should be introduced at the beginning of the paper, such as in figure 1.
275 \textcolor{blue}{Answer: We have changed it in the paper and added to page 6.}
278 \item Authors comment whether (and how) the proposed methods can be applied/extended to other programming models and/or platform, such as mapreduce, heterogeneous cluster with CPU+GPU.
281 \textcolor{blue}{Answer: The proposed method can only be applied to parallel programming with iteration
282 and with or without message passing. Indeed, the proposed method can be applied to the parallel application with mapreduce if it is a regular application with iterations. Therefore, the time of each map and reduce operations (communications) and the computation times in the program must be computed at the first iterations to predict the energy consumption and the execution time. After, the proposed algorithm can be used as it to select the best frequencies.
283 The proposed method can be applied to a heterogeneous platform composed from GPUs and CPUs, since modern GPUs like CPUs allow the use of DVFS operation.}
286 \section{Questions and remarks of the third reviewer}
289 \item suggest the authors to use much larger size of nodes, instead of on 16 nodes, distributed on three clusters, to see the scalability of the energy saving
291 \textcolor{blue}{Answer: We have made the experiments not only on 16 nodes, but we have also made them over 32 nodes distributed over three clusters and in the near future we will apply the proposed method over a larger number of nodes.}
293 \item the energy saving is actually calculated by the quantitative formula instead of the real measurements. Can you have any discussions on the real measurements?
295 \textcolor{blue}{Answer: The scope of this paper is not mainly focuses on the energy measurements, but it focuses on modelling and optimizing the energy and performance of grid systems. The proposed energy model depends on the dynamic and static power values for each CPU. We have used a real power measurement tools allowed in Grid'5000 sites to measure the dynamic power consumption. Moreover, the real measurements are difficult for a grid platform when the nodes are geographically distributed. As a future work, it is interesting to compare the accuracy of the proposed energy model with a real instruments to measure the energy consumption for local clusters such as the measurement tools presented in \cite{2}.}
297 \item the overhead is not measured, can you present something on this as well to demonstrate what the authors claimed "has a small overhead and works without training or profiling"?
299 \textcolor{blue}{Answer: In the comparison section 6.5, we have presented the execution time of the algorithm when it is executed over 32 nodes distributed over three sites located at two different sites, it takes on average 0.01 $ms$. The algorithm works online without training which means it only uses the measured communication and computation times during the runtime and do not require any profiling or training executed before runtime.}
301 \bibliographystyle{plain}
302 \bibliography{ref.bib}
