
case of the RFR models, each combination of 7 hy-
perparameters was used. In case of the GBR models,
combinations of six hyperparameters were used and
in case of ABR only two hyperparameters were ana-
lyzed.
The actual value of the AC consumption is strictly
correlated with the actual number of execution tests.
This can be seen after the start of the ABR models
when the AC current increases significantly. Then af-
ter the end of ABR, GBR, and RFR the decrease of
AC is also visible.
It is also worth noting the sudden increase in the
AC near the 15th April while no new processes were
executed. This indicates that the specific combina-
tion of the hyperparameters during the ML tests might
require more computational power and therefore re-
quires more electrical power to execute them.
Fig. 4 presents the consumption of direct current
(DC) during ML tests. It is worth noticing that both
the AC and DC values have the same trends in the
changes in the values. Since the voltage of the DC
is significantly lower, the output values of the DC are
higher than those of the AC. Because of that, only
analyzing one of those figures will be enough.
In both figures 3 and 4 an interesting trend can be
seen about the difference in the current provided by
different power supplies. Three of them (Power Sup-
ply 1, Power Supply 3, Power Supply 4) are loaded
very similar, while Power Supply 2 is more loaded.
This was mainly due to the redundancy policy used in
the case (Smith et al., 2008).
The measured temperatures of the power supplies
during ML experiments are depicted in Fig. 5. In
most cases, the temperature of the power supply is
strongly correlated with the power generated by a par-
ticular unit. The temperatures range from 22°C to
35°C, which can be considered natural values (Ko-
lari
´
c et al., 2011). The interesting fact is that the tem-
perature values oscillate in time. The source of those
oscillations requires further investigation.
Information about available power, peripheral
power, reserve power, and total power is presented in
Figure 6. As can be seen, those values are not depen-
dent on the actual experiment running. Because of
that, they are not used for further examination.
4.2 NoSQL Datastore Experiment
The second experiment aimed to test distributed
NoSQL data storage, called Scalable Distributed
Two–Layered Data Structure (SD2DS) (Krechowicz
et al., 2016; Krechowicz et al., 2017). The main
feature of this data storage is the distribution of the
stored data and its metadata into two separate loca-
tions (buckets). This separation proves to increase
efficiency and allows the introduction of many addi-
tional features (Krechowicz, 2016). The tests consists
of 17 nodes that run storage buckets. 10 additional
nodes were used to run storage client processes. Dur-
ing the tests different data item sizes and different
numbers of clients were analyzed.
In figure 7 the values of the AC are presented
while performing the NoSQL experiments. The red
dashed lines indicate the division into separate tests
that use different configurations. The blue values in-
dicate the sizes of the data items currently examined,
while the red values indicate the number of clients in-
stances that simultaneously send requests to the dis-
tributed data storage. Due to the similarities between
AC and DC presented in the previous experiment, the
DC values were omitted. Since nodes on two chassis
were used to run SD2DS buckets as well as clients,
the 8 power supplies on both chassis were analyzed.
In this figure, many regular drops in the AC val-
ues are visible. They were caused by the nature
of the tests. Each separate test consists of insert-
ing new items, retrieving inserted items, and wait-
ing phase. The wait phases were required to ensure
that all socket connections are properly closed before
running the next experiment. In that scenario, the
next test is not affected by the previous test. This is
extremely important in an environment where many
connections are made simultaneously. As the number
of clients and sizes of the data items increases those
drops are less and less visible. Additionally slight in-
crease in the total value of the power is also visible as
the number of clients operates on the store (velocity
of the data) and data items sizes (volume of the data)
increases.
In the fig 8 the value of the AC is presented dur-
ing the failed experiment. In this case some random
exception happens that cause to crush 10 buckets so
clients could not be properly handled. The failed test
arises between the two dashed red lines in the area be-
tween the two dashed red lines. It can be clearly seen
that the failed test produces a different power con-
sumption profile than the correct experiments before
and after. The similar distortion in the temperature
profile during failed experiments can be seen in Fig.
9.
5 CONCLUSIONS
The purpose of the paper was to develop a framework
that can monitor the power consumption of the com-
pute cluster during the execution of distributed appli-
cations. The goal was achieved by web scraping of the
A Framework for Real-Time Monitoring of Power Consumption of Distributed Calculation on Computational Cluster
267