WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.750 --> 00:00:11.090
Hi. In this video we will introduce the dusk dashboard.

1
00:00:13.860 --> 00:00:17.290
Let's navigate to our dashboard then, uh, it sits, uh,

2
00:00:17.430 --> 00:00:20.770
on the port 8, 8, 8 9 on the local host. As we set it up,

3
00:00:23.800 --> 00:00:28.780
uh, the main and most useful tab is the status tab. As we see here,

4
00:00:29.530 --> 00:00:30.460
what you can see here,

5
00:00:33.180 --> 00:00:37.040
we see here how many gigabytes in total, uh, is used, um,

6
00:00:37.580 --> 00:00:42.060
and what is available in the cluster. We see that just, uh,

7
00:00:42.160 --> 00:00:47.020
by starting the cluster, uh, we already using uh, uh,

8
00:00:47.330 --> 00:00:49.420
more than 600 megabytes of memory.

9
00:00:51.840 --> 00:00:54.140
We see here the memory consumption per worker

10
00:00:56.240 --> 00:01:00.740
in task stream. We are able to see processing of tasks in a time series chart.

11
00:01:03.580 --> 00:01:07.320
In, uh, progress, uh, we will see the overall progress of the computations.

12
00:01:08.940 --> 00:01:12.240
And here in this section we see number of tasks, uh,

13
00:01:12.240 --> 00:01:15.840
which are currently in processing C P U utilization and other

14
00:01:20.490 --> 00:01:22.910
in workers' tab. We see information about our workers

15
00:01:27.450 --> 00:01:31.420
task stream is basically same as in the first tab, uh, status, uh,

16
00:01:31.420 --> 00:01:33.500
the time series chart of task processing.

17
00:01:38.230 --> 00:01:38.790
In, uh,

18
00:01:38.790 --> 00:01:42.610
system tab we have some information about our current state of the system

19
00:01:42.970 --> 00:01:43.803
resources.

20
00:01:48.160 --> 00:01:52.540
The profile tab, uh, is sometimes useful if you want to see which tasks, uh,

21
00:01:52.680 --> 00:01:56.420
are too long to calculate. Or if you want to, Deb, back your calculations

22
00:02:00.090 --> 00:02:00.840
in graph tab,

23
00:02:00.840 --> 00:02:05.790
we'll able to see the dust graph of currently running calculations. But,

24
00:02:05.970 --> 00:02:10.510
uh, if you have a big graph on many partitions rendering,

25
00:02:10.570 --> 00:02:13.870
it may be very slow or it might be not rendered at all.

26
00:02:14.490 --> 00:02:17.470
To explore the das graph is always better, uh,

27
00:02:17.650 --> 00:02:19.590
to do before you run the calculations.

28
00:02:23.900 --> 00:02:28.640
And in info tap we can get more information about locks and exceptions occurred

29
00:02:28.640 --> 00:02:32.520
in each of the worker. These might be sometimes useful when, uh,

30
00:02:32.590 --> 00:02:35.520
some of your workers crashes and you do not know why.

31
00:02:39.490 --> 00:02:43.110
And in Morett Tap we can get even more detailed informations about our cluster

32
00:02:43.290 --> 00:02:44.123
or running graph.

33
00:02:49.540 --> 00:02:53.520
In our next video, we will start to do analytics on the whole data,

34
00:02:53.900 --> 00:02:57.440
and we will see what is happening in the dashboard during calculations.
