WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.230 align:start position:0% [Music] 00:00:10.230 --> 00:00:10.240 align:start position:0% [Music] 00:00:10.240 --> 00:00:14.110 align:start position:0% [Music] all<00:00:10.440> right<00:00:11.000> let's<00:00:11.440> hear<00:00:11.639> it<00:00:11.799> for<00:00:12.240> zarra 00:00:14.110 --> 00:00:14.120 align:start position:0% all right let's hear it for zarra 00:00:14.120 --> 00:00:18.150 align:start position:0% all right let's hear it for zarra BMA<00:00:15.120> hi 00:00:18.150 --> 00:00:18.160 align:start position:0% 00:00:18.160 --> 00:00:21.790 align:start position:0% guys<00:00:19.160> so<00:00:19.760> we<00:00:19.960> worked<00:00:20.320> on<00:00:20.680> consensus<00:00:21.240> client 00:00:21.790 --> 00:00:21.800 align:start position:0% guys so we worked on consensus client 00:00:21.800 --> 00:00:25.390 align:start position:0% guys so we worked on consensus client performance<00:00:22.599> profiling<00:00:23.880> um<00:00:24.880> both<00:00:25.039> of<00:00:25.160> us<00:00:25.279> at 00:00:25.390 --> 00:00:25.400 align:start position:0% performance profiling um both of us at 00:00:25.400 --> 00:00:27.150 align:start position:0% performance profiling um both of us at the<00:00:25.480> simar<00:00:25.880> interest<00:00:26.320> starting<00:00:26.720> off<00:00:26.920> with 00:00:27.150 --> 00:00:27.160 align:start position:0% the simar interest starting off with 00:00:27.160 --> 00:00:29.349 align:start position:0% the simar interest starting off with grandine<00:00:27.960> and<00:00:28.160> branching<00:00:28.599> out<00:00:28.760> a<00:00:28.880> bit<00:00:29.080> as<00:00:29.199> you 00:00:29.349 --> 00:00:29.359 align:start position:0% grandine and branching out a bit as you 00:00:29.359 --> 00:00:32.470 align:start position:0% grandine and branching out a bit as you do<00:00:29.560> during<00:00:29.759> a<00:00:30.240> work<00:00:30.480> on<00:00:30.599> a<00:00:31.119> project<00:00:32.119> um<00:00:32.279> there's 00:00:32.470 --> 00:00:32.480 align:start position:0% do during a work on a project um there's 00:00:32.480 --> 00:00:34.590 align:start position:0% do during a work on a project um there's a<00:00:32.599> couple<00:00:32.800> of<00:00:32.880> repos<00:00:33.320> listed<00:00:33.760> there<00:00:34.320> two<00:00:34.480> of 00:00:34.590 --> 00:00:34.600 align:start position:0% a couple of repos listed there two of 00:00:34.600 --> 00:00:36.069 align:start position:0% a couple of repos listed there two of them<00:00:34.719> are<00:00:34.840> on<00:00:35.000> GitHub<00:00:35.520> because<00:00:35.760> that's<00:00:35.879> where 00:00:36.069 --> 00:00:36.079 align:start position:0% them are on GitHub because that's where 00:00:36.079 --> 00:00:39.229 align:start position:0% them are on GitHub because that's where everybody<00:00:36.440> else<00:00:36.840> is<00:00:37.840> and<00:00:38.160> I<00:00:38.360> myself<00:00:38.719> prefer<00:00:39.000> G 00:00:39.229 --> 00:00:39.239 align:start position:0% everybody else is and I myself prefer G 00:00:39.239 --> 00:00:42.310 align:start position:0% everybody else is and I myself prefer G laap<00:00:39.559> so<00:00:39.879> I<00:00:40.440> threw<00:00:40.800> that<00:00:40.920> in<00:00:41.559> um<00:00:42.000> I'm<00:00:42.079> going<00:00:42.200> to 00:00:42.310 --> 00:00:42.320 align:start position:0% laap so I threw that in um I'm going to 00:00:42.320 --> 00:00:44.430 align:start position:0% laap so I threw that in um I'm going to hand<00:00:42.480> it<00:00:42.600> to<00:00:42.879> Bulma<00:00:43.320> who's<00:00:43.640> GNA<00:00:44.120> take<00:00:44.280> the 00:00:44.430 --> 00:00:44.440 align:start position:0% hand it to Bulma who's GNA take the 00:00:44.440 --> 00:00:49.310 align:start position:0% hand it to Bulma who's GNA take the first<00:00:44.680> bit<00:00:45.320> okay<00:00:46.000> hello<00:00:47.000> hello<00:00:47.600> okay<00:00:48.039> sorry<00:00:49.039> um 00:00:49.310 --> 00:00:49.320 align:start position:0% first bit okay hello hello okay sorry um 00:00:49.320 --> 00:00:51.990 align:start position:0% first bit okay hello hello okay sorry um my<00:00:49.440> name<00:00:49.600> is<00:00:49.800> Messi<00:00:50.600> and<00:00:51.079> I'm<00:00:51.320> here<00:00:51.480> to<00:00:51.640> make<00:00:51.760> a 00:00:51.990 --> 00:00:52.000 align:start position:0% my name is Messi and I'm here to make a 00:00:52.000 --> 00:00:55.029 align:start position:0% my name is Messi and I'm here to make a pres<00:00:52.640> presentation<00:00:53.640> Although<00:00:54.239> our<00:00:54.520> projects 00:00:55.029 --> 00:00:55.039 align:start position:0% pres presentation Although our projects 00:00:55.039 --> 00:00:57.670 align:start position:0% pres presentation Although our projects shifted<00:00:55.600> a<00:00:55.760> little<00:00:56.079> bit<00:00:56.719> um<00:00:56.920> the<00:00:57.079> initial<00:00:57.440> goal 00:00:57.670 --> 00:00:57.680 align:start position:0% shifted a little bit um the initial goal 00:00:57.680 --> 00:01:00.349 align:start position:0% shifted a little bit um the initial goal was<00:00:57.840> to<00:00:58.120> work<00:00:58.320> on<00:00:58.600> security<00:00:59.000> and<00:00:59.199> testing<00:01:00.120> but 00:01:00.349 --> 00:01:00.359 align:start position:0% was to work on security and testing but 00:01:00.359 --> 00:01:04.070 align:start position:0% was to work on security and testing but due<00:01:00.559> to<00:01:00.840> some<00:01:01.680> um<00:01:02.640> uh<00:01:02.920> I<00:01:03.079> underestimated<00:01:03.800> some 00:01:04.070 --> 00:01:04.080 align:start position:0% due to some um uh I underestimated some 00:01:04.080 --> 00:01:07.070 align:start position:0% due to some um uh I underestimated some things<00:01:05.000> and<00:01:05.159> so<00:01:05.400> that<00:01:05.519> was<00:01:06.000> I<00:01:06.119> had<00:01:06.280> to<00:01:06.520> focus<00:01:06.840> on 00:01:07.070 --> 00:01:07.080 align:start position:0% things and so that was I had to focus on 00:01:07.080 --> 00:01:09.230 align:start position:0% things and so that was I had to focus on um<00:01:07.240> performance<00:01:07.680> analysis<00:01:08.520> a<00:01:08.720> comparative 00:01:09.230 --> 00:01:09.240 align:start position:0% um performance analysis a comparative 00:01:09.240 --> 00:01:17.469 align:start position:0% um performance analysis a comparative analysis<00:01:09.759> between<00:01:10.240> the<00:01:10.360> cons<00:01:11.159> client<00:01:12.159> oh 00:01:17.469 --> 00:01:17.479 align:start position:0% 00:01:17.479 --> 00:01:21.030 align:start position:0% okay<00:01:18.479> so 00:01:21.030 --> 00:01:21.040 align:start position:0% okay so 00:01:21.040 --> 00:01:24.630 align:start position:0% okay so okay<00:01:22.040> sorry<00:01:22.640> um<00:01:23.079> so<00:01:23.600> the<00:01:23.759> initial<00:01:24.200> goal<00:01:24.400> was<00:01:24.520> to 00:01:24.630 --> 00:01:24.640 align:start position:0% okay sorry um so the initial goal was to 00:01:24.640 --> 00:01:26.469 align:start position:0% okay sorry um so the initial goal was to do<00:01:24.840> a<00:01:25.040> security<00:01:25.520> and<00:01:25.799> reliability<00:01:26.360> of 00:01:26.469 --> 00:01:26.479 align:start position:0% do a security and reliability of 00:01:26.479 --> 00:01:28.310 align:start position:0% do a security and reliability of grinding<00:01:27.000> and<00:01:27.240> then<00:01:27.640> there<00:01:27.759> was<00:01:27.880> a<00:01:27.960> shift<00:01:28.159> in 00:01:28.310 --> 00:01:28.320 align:start position:0% grinding and then there was a shift in 00:01:28.320 --> 00:01:30.950 align:start position:0% grinding and then there was a shift in Focus<00:01:28.720> which<00:01:28.920> transitioned<00:01:29.560> to<00:01:29.920> to<00:01:30.520> profiling 00:01:30.950 --> 00:01:30.960 align:start position:0% Focus which transitioned to to profiling 00:01:30.960 --> 00:01:32.749 align:start position:0% Focus which transitioned to to profiling multiple<00:01:31.360> clients<00:01:31.799> due<00:01:31.960> to<00:01:32.320> technical 00:01:32.749 --> 00:01:32.759 align:start position:0% multiple clients due to technical 00:01:32.759 --> 00:01:35.030 align:start position:0% multiple clients due to technical challenges<00:01:33.360> which<00:01:33.560> I 00:01:35.030 --> 00:01:35.040 align:start position:0% challenges which I 00:01:35.040 --> 00:01:38.990 align:start position:0% challenges which I faced<00:01:36.040> oh<00:01:36.399> okay 00:01:38.990 --> 00:01:39.000 align:start position:0% 00:01:39.000 --> 00:01:43.270 align:start position:0% sorry<00:01:40.000> so<00:01:40.560> um<00:01:40.880> first<00:01:41.119> of<00:01:41.280> all<00:01:41.680> I<00:01:42.439> used<00:01:42.759> so<00:01:42.960> many 00:01:43.270 --> 00:01:43.280 align:start position:0% sorry so um first of all I used so many 00:01:43.280 --> 00:01:45.149 align:start position:0% sorry so um first of all I used so many performance<00:01:43.759> security<00:01:44.439> um 00:01:45.149 --> 00:01:45.159 align:start position:0% performance security um 00:01:45.159 --> 00:01:47.270 align:start position:0% performance security um tools<00:01:46.159> the<00:01:46.240> ones<00:01:46.479> that<00:01:46.600> stood<00:01:46.840> out<00:01:46.960> to<00:01:47.040> me<00:01:47.159> was 00:01:47.270 --> 00:01:47.280 align:start position:0% tools the ones that stood out to me was 00:01:47.280 --> 00:01:49.469 align:start position:0% tools the ones that stood out to me was a<00:01:47.399> flame<00:01:47.680> graph<00:01:48.000> and<00:01:48.119> then<00:01:48.360> it<00:01:48.840> implementing<00:01:49.320> a 00:01:49.469 --> 00:01:49.479 align:start position:0% a flame graph and then it implementing a 00:01:49.479 --> 00:01:52.109 align:start position:0% a flame graph and then it implementing a timing<00:01:49.759> metrix<00:01:50.240> on<00:01:50.799> grinding<00:01:51.799> this<00:01:51.880> is 00:01:52.109 --> 00:01:52.119 align:start position:0% timing metrix on grinding this is 00:01:52.119 --> 00:01:55.270 align:start position:0% timing metrix on grinding this is example<00:01:52.479> of<00:01:52.680> what<00:01:52.840> a<00:01:52.960> flame<00:01:53.280> graph<00:01:53.600> looks<00:01:54.280> like 00:01:55.270 --> 00:01:55.280 align:start position:0% example of what a flame graph looks like 00:01:55.280 --> 00:01:56.950 align:start position:0% example of what a flame graph looks like uh<00:01:55.560> although<00:01:55.960> it's<00:01:56.079> not<00:01:56.280> quite<00:01:56.479> readable 00:01:56.950 --> 00:01:56.960 align:start position:0% uh although it's not quite readable 00:01:56.960 --> 00:01:58.550 align:start position:0% uh although it's not quite readable because<00:01:57.240> you<00:01:57.360> have<00:01:57.520> to<00:01:57.680> like<00:01:57.880> click<00:01:58.159> in<00:01:58.360> and 00:01:58.550 --> 00:01:58.560 align:start position:0% because you have to like click in and 00:01:58.560 --> 00:02:03.310 align:start position:0% because you have to like click in and then<00:01:58.799> out<00:01:59.119> to<00:01:59.360> really<00:02:00.079> view<00:02:01.079> but<00:02:02.000> okay<00:02:03.000> so 00:02:03.310 --> 00:02:03.320 align:start position:0% then out to really view but okay so 00:02:03.320 --> 00:02:05.429 align:start position:0% then out to really view but okay so looking<00:02:03.600> at<00:02:03.759> this<00:02:03.920> Stacks<00:02:04.640> um<00:02:04.799> grinding<00:02:05.280> is 00:02:05.429 --> 00:02:05.439 align:start position:0% looking at this Stacks um grinding is 00:02:05.439 --> 00:02:07.389 align:start position:0% looking at this Stacks um grinding is actually<00:02:05.719> performing<00:02:06.159> very<00:02:06.360> well<00:02:06.640> from<00:02:07.240> the 00:02:07.389 --> 00:02:07.399 align:start position:0% actually performing very well from the 00:02:07.399 --> 00:02:08.869 align:start position:0% actually performing very well from the stock<00:02:07.719> overview<00:02:08.160> although<00:02:08.399> there's<00:02:08.560> a<00:02:08.640> drop 00:02:08.869 --> 00:02:08.879 align:start position:0% stock overview although there's a drop 00:02:08.879 --> 00:02:12.070 align:start position:0% stock overview although there's a drop down<00:02:09.080> from<00:02:09.560> the<00:02:09.720> Tokyo<00:02:10.080> run<00:02:10.360> time<00:02:10.640> which<00:02:11.160> is<00:02:11.319> at 00:02:12.070 --> 00:02:12.080 align:start position:0% down from the Tokyo run time which is at 00:02:12.080 --> 00:02:16.430 align:start position:0% down from the Tokyo run time which is at 61.79<00:02:13.080> per.<00:02:14.000> which<00:02:14.319> had<00:02:14.519> a<00:02:14.680> minus<00:02:15.120> 35%<00:02:16.120> drop 00:02:16.430 --> 00:02:16.440 align:start position:0% 61.79 per. which had a minus 35% drop 00:02:16.440 --> 00:02:18.670 align:start position:0% 61.79 per. which had a minus 35% drop down<00:02:17.120> so<00:02:17.400> the<00:02:17.599> key<00:02:17.800> observation<00:02:18.319> here<00:02:18.480> is 00:02:18.670 --> 00:02:18.680 align:start position:0% down so the key observation here is 00:02:18.680 --> 00:02:21.910 align:start position:0% down so the key observation here is there<00:02:18.800> is<00:02:18.959> a<00:02:19.120> high<00:02:19.319> Trend<00:02:19.760> utilization<00:02:20.760> on<00:02:21.040> 97% 00:02:21.910 --> 00:02:21.920 align:start position:0% there is a high Trend utilization on 97% 00:02:21.920 --> 00:02:24.070 align:start position:0% there is a high Trend utilization on 97% in<00:02:22.040> system<00:02:22.360> Trends<00:02:22.640> and<00:02:22.800> initial<00:02:23.160> setup 00:02:24.070 --> 00:02:24.080 align:start position:0% in system Trends and initial setup 00:02:24.080 --> 00:02:26.670 align:start position:0% in system Trends and initial setup significant<00:02:24.599> drop<00:02:24.840> down<00:02:25.000> to<00:02:25.319> 62<00:02:25.920> in<00:02:26.080> Tokyo<00:02:26.400> R 00:02:26.670 --> 00:02:26.680 align:start position:0% significant drop down to 62 in Tokyo R 00:02:26.680 --> 00:02:29.630 align:start position:0% significant drop down to 62 in Tokyo R time<00:02:27.200> operations<00:02:28.200> and<00:02:28.319> then<00:02:28.560> a<00:02:28.920> consistent 00:02:29.630 --> 00:02:29.640 align:start position:0% time operations and then a consistent 00:02:29.640 --> 00:02:32.670 align:start position:0% time operations and then a consistent per<00:02:29.879> performance<00:02:30.319> across<00:02:30.640> to<00:02:31.440> tax<00:02:31.800> management 00:02:32.670 --> 00:02:32.680 align:start position:0% per performance across to tax management 00:02:32.680 --> 00:02:34.270 align:start position:0% per performance across to tax management also<00:02:33.000> multi<00:02:33.280> trained<00:02:33.560> worker<00:02:33.840> execution 00:02:34.270 --> 00:02:34.280 align:start position:0% also multi trained worker execution 00:02:34.280 --> 00:02:40.990 align:start position:0% also multi trained worker execution showing<00:02:34.720> similar<00:02:35.440> patterns<00:02:35.840> in<00:02:36.000> different 00:02:40.990 --> 00:02:41.000 align:start position:0% 00:02:41.000 --> 00:02:46.390 align:start position:0% narratives<00:02:42.000> is 00:02:46.390 --> 00:02:46.400 align:start position:0% 00:02:46.400 --> 00:02:51.190 align:start position:0% work<00:02:47.400> okay 00:02:51.190 --> 00:02:51.200 align:start position:0% 00:02:51.200 --> 00:02:53.390 align:start position:0% sorry<00:02:52.200> so 00:02:53.390 --> 00:02:53.400 align:start position:0% sorry so 00:02:53.400 --> 00:02:57.390 align:start position:0% sorry so um<00:02:54.400> this<00:02:54.560> is<00:02:55.239> the<00:02:55.519> 35%<00:02:56.440> looking<00:02:56.720> at<00:02:57.000> the<00:02:57.120> system 00:02:57.390 --> 00:02:57.400 align:start position:0% um this is the 35% looking at the system 00:02:57.400 --> 00:02:59.550 align:start position:0% um this is the 35% looking at the system trade<00:02:57.720> level<00:02:57.959> which<00:02:58.040> is<00:02:58.159> 97%<00:02:58.920> then<00:02:59.120> too<00:02:59.440> one 00:02:59.550 --> 00:02:59.560 align:start position:0% trade level which is 97% then too one 00:02:59.560 --> 00:03:02.750 align:start position:0% trade level which is 97% then too one time<00:02:59.680> which<00:02:59.760> is<00:02:59.840> which<00:02:59.879> is<00:03:00.400> 62%<00:03:01.400> and<00:03:01.560> then<00:03:01.760> the 00:03:02.750 --> 00:03:02.760 align:start position:0% time which is which is 62% and then the 00:03:02.760 --> 00:03:06.270 align:start position:0% time which is which is 62% and then the which<00:03:03.000> identifies<00:03:03.480> a<00:03:03.640> 35%<00:03:04.480> drop<00:03:04.760> down<00:03:05.480> so<00:03:05.879> the 00:03:06.270 --> 00:03:06.280 align:start position:0% which identifies a 35% drop down so the 00:03:06.280 --> 00:03:07.990 align:start position:0% which identifies a 35% drop down so the there<00:03:06.360> is<00:03:06.680> the<00:03:06.840> the<00:03:06.959> cliff<00:03:07.280> there<00:03:07.440> is<00:03:07.599> kind<00:03:07.720> of 00:03:07.990 --> 00:03:08.000 align:start position:0% there is the the cliff there is kind of 00:03:08.000 --> 00:03:10.270 align:start position:0% there is the the cliff there is kind of huge<00:03:08.640> and<00:03:08.959> then<00:03:09.120> the<00:03:09.280> high<00:03:09.480> performance<00:03:09.920> areas 00:03:10.270 --> 00:03:10.280 align:start position:0% huge and then the high performance areas 00:03:10.280 --> 00:03:12.550 align:start position:0% huge and then the high performance areas are<00:03:10.720> trade<00:03:11.040> initialization<00:03:11.959> system<00:03:12.280> level 00:03:12.550 --> 00:03:12.560 align:start position:0% are trade initialization system level 00:03:12.560 --> 00:03:14.750 align:start position:0% are trade initialization system level operations<00:03:13.120> and<00:03:13.360> then<00:03:13.760> Co<00:03:14.000> Trend<00:03:14.280> management 00:03:14.750 --> 00:03:14.760 align:start position:0% operations and then Co Trend management 00:03:14.760 --> 00:03:16.710 align:start position:0% operations and then Co Trend management which<00:03:15.000> gred<00:03:15.519> pretty<00:03:15.840> handled<00:03:16.239> very<00:03:16.400> well<00:03:16.560> and 00:03:16.710 --> 00:03:16.720 align:start position:0% which gred pretty handled very well and 00:03:16.720 --> 00:03:18.309 align:start position:0% which gred pretty handled very well and then<00:03:16.840> performed<00:03:17.200> very<00:03:17.319> well<00:03:17.440> in<00:03:17.560> that<00:03:17.760> aspect 00:03:18.309 --> 00:03:18.319 align:start position:0% then performed very well in that aspect 00:03:18.319 --> 00:03:20.509 align:start position:0% then performed very well in that aspect so<00:03:18.519> areas<00:03:18.840> of<00:03:19.319> Investigation<00:03:20.239> okay<00:03:20.360> a 00:03:20.509 --> 00:03:20.519 align:start position:0% so areas of Investigation okay a 00:03:20.519 --> 00:03:23.110 align:start position:0% so areas of Investigation okay a disclaimer<00:03:21.080> this<00:03:21.200> is<00:03:21.360> a<00:03:21.519> research<00:03:22.000> project<00:03:22.720> is 00:03:23.110 --> 00:03:23.120 align:start position:0% disclaimer this is a research project is 00:03:23.120 --> 00:03:24.910 align:start position:0% disclaimer this is a research project is still<00:03:23.920> I<00:03:23.959> will<00:03:24.120> call<00:03:24.239> it<00:03:24.360> the<00:03:24.480> research 00:03:24.910 --> 00:03:24.920 align:start position:0% still I will call it the research 00:03:24.920 --> 00:03:27.190 align:start position:0% still I will call it the research because<00:03:25.400> so<00:03:25.560> many<00:03:25.760> things<00:03:26.000> can<00:03:26.200> change<00:03:26.640> and 00:03:27.190 --> 00:03:27.200 align:start position:0% because so many things can change and 00:03:27.200 --> 00:03:30.390 align:start position:0% because so many things can change and then<00:03:28.200> I<00:03:28.360> might<00:03:28.720> be<00:03:28.879> wrong<00:03:29.159> in<00:03:29.280> some<00:03:29.480> cases 00:03:30.390 --> 00:03:30.400 align:start position:0% then I might be wrong in some cases 00:03:30.400 --> 00:03:33.149 align:start position:0% then I might be wrong in some cases so<00:03:31.159> areas<00:03:31.480> of<00:03:31.879> Investigation<00:03:32.480> for<00:03:32.640> me<00:03:32.799> is<00:03:32.920> a 00:03:33.149 --> 00:03:33.159 align:start position:0% so areas of Investigation for me is a 00:03:33.159 --> 00:03:35.789 align:start position:0% so areas of Investigation for me is a Tokyo<00:03:33.599> TI<00:03:33.879> sheding<00:03:34.480> which<00:03:34.560> is<00:03:34.680> at<00:03:34.879> 62%<00:03:35.680> and 00:03:35.789 --> 00:03:35.799 align:start position:0% Tokyo TI sheding which is at 62% and 00:03:35.799 --> 00:03:37.830 align:start position:0% Tokyo TI sheding which is at 62% and then<00:03:35.920> the<00:03:36.080> sign<00:03:36.360> corron<00:03:36.640> time<00:03:37.159> overhead<00:03:37.720> and 00:03:37.830 --> 00:03:37.840 align:start position:0% then the sign corron time overhead and 00:03:37.840 --> 00:03:40.949 align:start position:0% then the sign corron time overhead and the<00:03:38.040> tax<00:03:38.680> profiling 00:03:40.949 --> 00:03:40.959 align:start position:0% the tax profiling 00:03:40.959 --> 00:03:43.550 align:start position:0% the tax profiling efficiency<00:03:41.959> and<00:03:42.439> um<00:03:42.599> talking<00:03:42.959> about<00:03:43.319> the 00:03:43.550 --> 00:03:43.560 align:start position:0% efficiency and um talking about the 00:03:43.560 --> 00:03:47.350 align:start position:0% efficiency and um talking about the timing<00:03:43.920> metrics<00:03:44.599> which<00:03:44.920> I<00:03:45.319> had<00:03:45.519> to 00:03:47.350 --> 00:03:47.360 align:start position:0% timing metrics which I had to 00:03:47.360 --> 00:03:50.789 align:start position:0% timing metrics which I had to implement<00:03:48.360> for<00:03:48.599> now<00:03:49.080> I<00:03:49.280> okay<00:03:49.519> I<00:03:49.680> was<00:03:50.239> Sal 00:03:50.789 --> 00:03:50.799 align:start position:0% implement for now I okay I was Sal 00:03:50.799 --> 00:03:51.949 align:start position:0% implement for now I okay I was Sal suggested<00:03:51.239> that<00:03:51.360> I<00:03:51.480> have<00:03:51.640> to<00:03:51.720> do<00:03:51.840> a 00:03:51.949 --> 00:03:51.959 align:start position:0% suggested that I have to do a 00:03:51.959 --> 00:03:54.429 align:start position:0% suggested that I have to do a comparative<00:03:52.480> analysis<00:03:52.959> between<00:03:53.920> um<00:03:54.319> um 00:03:54.429 --> 00:03:54.439 align:start position:0% comparative analysis between um um 00:03:54.439 --> 00:03:56.670 align:start position:0% comparative analysis between um um grinding<00:03:54.920> and<00:03:55.040> then<00:03:55.239> Lighthouse<00:03:55.840> so<00:03:56.239> for<00:03:56.439> now 00:03:56.670 --> 00:03:56.680 align:start position:0% grinding and then Lighthouse so for now 00:03:56.680 --> 00:03:59.429 align:start position:0% grinding and then Lighthouse so for now I<00:03:56.920> only<00:03:57.159> have<00:03:57.319> the<00:03:57.519> data<00:03:57.799> on<00:03:58.200> grinding<00:03:58.959> and<00:03:59.239> I'm 00:03:59.429 --> 00:03:59.439 align:start position:0% I only have the data on grinding and I'm 00:03:59.439 --> 00:04:01.630 align:start position:0% I only have the data on grinding and I'm yet<00:03:59.799> to<00:03:59.920> produce<00:04:00.159> the<00:04:00.280> data<00:04:00.439> for<00:04:00.599> lious<00:04:01.040> to 00:04:01.630 --> 00:04:01.640 align:start position:0% yet to produce the data for lious to 00:04:01.640 --> 00:04:03.589 align:start position:0% yet to produce the data for lious to properly<00:04:02.040> do<00:04:02.439> a<00:04:02.560> comparative<00:04:03.040> analysis<00:04:03.480> but 00:04:03.589 --> 00:04:03.599 align:start position:0% properly do a comparative analysis but 00:04:03.599 --> 00:04:05.509 align:start position:0% properly do a comparative analysis but this<00:04:03.680> is<00:04:03.840> basically<00:04:04.239> how<00:04:04.720> the<00:04:04.920> data<00:04:05.200> looks 00:04:05.509 --> 00:04:05.519 align:start position:0% this is basically how the data looks 00:04:05.519 --> 00:04:08.910 align:start position:0% this is basically how the data looks like<00:04:05.799> and<00:04:06.040> I'm<00:04:06.319> hoping<00:04:06.560> to<00:04:06.760> use<00:04:07.040> this<00:04:07.680> to<00:04:08.680> do 00:04:08.910 --> 00:04:08.920 align:start position:0% like and I'm hoping to use this to do 00:04:08.920 --> 00:04:12.069 align:start position:0% like and I'm hoping to use this to do more<00:04:09.239> investigation<00:04:09.959> on<00:04:10.439> um<00:04:10.840> formal<00:04:11.680> to<00:04:11.840> do 00:04:12.069 --> 00:04:12.079 align:start position:0% more investigation on um formal to do 00:04:12.079 --> 00:04:14.869 align:start position:0% more investigation on um formal to do more<00:04:12.280> analysis<00:04:12.720> on<00:04:12.879> formal<00:04:13.720> verification<00:04:14.519> and 00:04:14.869 --> 00:04:14.879 align:start position:0% more analysis on formal verification and 00:04:14.879 --> 00:04:18.550 align:start position:0% more analysis on formal verification and U<00:04:15.040> foren<00:04:15.920> creating<00:04:16.320> a<00:04:16.479> targeted<00:04:16.919> foren<00:04:17.560> and 00:04:18.550 --> 00:04:18.560 align:start position:0% U foren creating a targeted foren and 00:04:18.560 --> 00:04:22.670 align:start position:0% U foren creating a targeted foren and what's<00:04:18.759> it<00:04:19.160> called<00:04:20.160> primtive<00:04:20.799> analysis<00:04:21.799> sorry 00:04:22.670 --> 00:04:22.680 align:start position:0% what's it called primtive analysis sorry 00:04:22.680 --> 00:04:26.550 align:start position:0% what's it called primtive analysis sorry and<00:04:22.960> then<00:04:23.360> hold 00:04:26.550 --> 00:04:26.560 align:start position:0% 00:04:26.560 --> 00:04:30.070 align:start position:0% on<00:04:27.560> so<00:04:27.919> the<00:04:28.080> reason<00:04:28.479> why<00:04:28.840> I<00:04:29.039> have<00:04:29.240> to<00:04:29.440> use<00:04:29.720> use 00:04:30.070 --> 00:04:30.080 align:start position:0% on so the reason why I have to use use 00:04:30.080 --> 00:04:32.189 align:start position:0% on so the reason why I have to use use tools<00:04:30.440> like<00:04:30.600> the<00:04:30.680> frame<00:04:30.919> graph<00:04:31.120> and<00:04:31.240> the<00:04:31.360> time 00:04:32.189 --> 00:04:32.199 align:start position:0% tools like the frame graph and the time 00:04:32.199 --> 00:04:35.790 align:start position:0% tools like the frame graph and the time um<00:04:33.000> the<00:04:33.280> timing<00:04:33.759> metrics<00:04:34.240> was<00:04:34.400> to<00:04:35.039> help<00:04:35.240> me 00:04:35.790 --> 00:04:35.800 align:start position:0% um the timing metrics was to help me 00:04:35.800 --> 00:04:37.749 align:start position:0% um the timing metrics was to help me understand<00:04:36.080> more<00:04:36.360> about<00:04:36.800> the<00:04:36.960> consen<00:04:37.440> client 00:04:37.749 --> 00:04:37.759 align:start position:0% understand more about the consen client 00:04:37.759 --> 00:04:39.550 align:start position:0% understand more about the consen client because<00:04:38.039> I<00:04:38.479> really 00:04:39.550 --> 00:04:39.560 align:start position:0% because I really 00:04:39.560 --> 00:04:42.430 align:start position:0% because I really underestimated<00:04:40.560> what<00:04:41.039> it<00:04:41.240> is<00:04:41.520> to<00:04:41.759> force<00:04:42.240> and 00:04:42.430 --> 00:04:42.440 align:start position:0% underestimated what it is to force and 00:04:42.440 --> 00:04:45.029 align:start position:0% underestimated what it is to force and build<00:04:42.960> um<00:04:43.280> a<00:04:43.400> a<00:04:43.520> forer<00:04:44.199> for<00:04:44.479> a<00:04:44.600> conscious 00:04:45.029 --> 00:04:45.039 align:start position:0% build um a a forer for a conscious 00:04:45.039 --> 00:04:46.950 align:start position:0% build um a a forer for a conscious client<00:04:45.360> because<00:04:45.880> coming<00:04:46.120> from<00:04:46.280> a<00:04:46.440> security<00:04:46.840> a 00:04:46.950 --> 00:04:46.960 align:start position:0% client because coming from a security a 00:04:46.960 --> 00:04:48.310 align:start position:0% client because coming from a security a smart<00:04:47.199> contous<00:04:47.520> security<00:04:47.880> background<00:04:48.240> I 00:04:48.310 --> 00:04:48.320 align:start position:0% smart contous security background I 00:04:48.320 --> 00:04:50.749 align:start position:0% smart contous security background I thought<00:04:48.520> it<00:04:48.639> was<00:04:48.800> the<00:04:48.960> same<00:04:49.680> perspective<00:04:50.360> but 00:04:50.749 --> 00:04:50.759 align:start position:0% thought it was the same perspective but 00:04:50.759 --> 00:04:53.430 align:start position:0% thought it was the same perspective but I<00:04:50.880> was<00:04:51.080> proven<00:04:51.560> wrong<00:04:52.400> and<00:04:52.600> the<00:04:52.800> complexity 00:04:53.430 --> 00:04:53.440 align:start position:0% I was proven wrong and the complexity 00:04:53.440 --> 00:04:56.390 align:start position:0% I was proven wrong and the complexity was<00:04:53.960> overwhelming<00:04:54.960> but<00:04:55.400> using<00:04:55.720> this<00:04:55.960> analysis 00:04:56.390 --> 00:04:56.400 align:start position:0% was overwhelming but using this analysis 00:04:56.400 --> 00:04:58.189 align:start position:0% was overwhelming but using this analysis and<00:04:56.560> using<00:04:56.800> this<00:04:57.000> data<00:04:57.360> I<00:04:57.440> think<00:04:57.639> I'll<00:04:57.840> be<00:04:57.960> able 00:04:58.189 --> 00:04:58.199 align:start position:0% and using this data I think I'll be able 00:04:58.199 --> 00:05:00.790 align:start position:0% and using this data I think I'll be able to<00:04:58.479> Pro<00:04:58.800> to<00:04:59.360> pre<00:04:59.759> produce<00:05:00.160> and<00:05:00.320> to<00:05:00.479> come<00:05:00.639> up 00:05:00.790 --> 00:05:00.800 align:start position:0% to Pro to pre produce and to come up 00:05:00.800 --> 00:05:03.629 align:start position:0% to Pro to pre produce and to come up with<00:05:00.880> a<00:05:01.080> strategy<00:05:01.639> in<00:05:02.080> in<00:05:02.199> order<00:05:02.520> to<00:05:03.240> have<00:05:03.479> a 00:05:03.629 --> 00:05:03.639 align:start position:0% with a strategy in in order to have a 00:05:03.639 --> 00:05:06.230 align:start position:0% with a strategy in in order to have a for<00:05:03.960> to<00:05:04.080> build<00:05:04.320> a<00:05:04.440> fora<00:05:05.120> which<00:05:05.280> has<00:05:05.400> to<00:05:05.560> do<00:05:05.720> with 00:05:06.230 --> 00:05:06.240 align:start position:0% for to build a fora which has to do with 00:05:06.240 --> 00:05:09.790 align:start position:0% for to build a fora which has to do with um<00:05:07.240> making<00:05:07.520> it<00:05:08.000> a<00:05:08.160> targeted<00:05:08.560> fora<00:05:09.120> and<00:05:09.360> also 00:05:09.790 --> 00:05:09.800 align:start position:0% um making it a targeted fora and also 00:05:09.800 --> 00:05:11.710 align:start position:0% um making it a targeted fora and also for<00:05:10.000> formal<00:05:10.360> verification<00:05:11.320> because<00:05:11.560> I 00:05:11.710 --> 00:05:11.720 align:start position:0% for formal verification because I 00:05:11.720 --> 00:05:14.550 align:start position:0% for formal verification because I understood<00:05:12.160> that<00:05:12.680> um<00:05:13.080> there<00:05:13.240> is<00:05:13.400> no<00:05:13.639> much<00:05:14.199> um 00:05:14.550 --> 00:05:14.560 align:start position:0% understood that um there is no much um 00:05:14.560 --> 00:05:16.909 align:start position:0% understood that um there is no much um um<00:05:14.840> um<00:05:15.160> um<00:05:15.440> work<00:05:15.759> on<00:05:15.880> formal<00:05:16.160> verification<00:05:16.680> on 00:05:16.909 --> 00:05:16.919 align:start position:0% um um um work on formal verification on 00:05:16.919 --> 00:05:19.629 align:start position:0% um um um work on formal verification on ethereum<00:05:17.360> cons<00:05:18.000> client<00:05:19.000> thank<00:05:19.160> you<00:05:19.360> I<00:05:19.479> can 00:05:19.629 --> 00:05:19.639 align:start position:0% ethereum cons client thank you I can 00:05:19.639 --> 00:05:30.070 align:start position:0% ethereum cons client thank you I can hand<00:05:19.759> it<00:05:19.880> over<00:05:20.080> to<00:05:20.240> you 00:05:30.070 --> 00:05:30.080 align:start position:0% 00:05:30.080 --> 00:05:33.029 align:start position:0% so<00:05:30.880> small<00:05:31.160> premise<00:05:31.560> to<00:05:31.720> the<00:05:31.880> second<00:05:32.160> part<00:05:32.639> so 00:05:33.029 --> 00:05:33.039 align:start position:0% so small premise to the second part so 00:05:33.039 --> 00:05:34.350 align:start position:0% so small premise to the second part so as<00:05:33.120> I<00:05:33.280> mentioned<00:05:33.639> we<00:05:33.759> initially<00:05:34.039> started 00:05:34.350 --> 00:05:34.360 align:start position:0% as I mentioned we initially started 00:05:34.360 --> 00:05:36.029 align:start position:0% as I mentioned we initially started working<00:05:34.600> on<00:05:34.759> grandine<00:05:35.560> it<00:05:35.680> was<00:05:35.759> a<00:05:35.840> slight 00:05:36.029 --> 00:05:36.039 align:start position:0% working on grandine it was a slight 00:05:36.039 --> 00:05:38.150 align:start position:0% working on grandine it was a slight shift<00:05:36.240> in<00:05:36.400> Focus<00:05:37.039> transitioned<00:05:37.680> to<00:05:37.919> doing 00:05:38.150 --> 00:05:38.160 align:start position:0% shift in Focus transitioned to doing 00:05:38.160 --> 00:05:40.070 align:start position:0% shift in Focus transitioned to doing this<00:05:38.440> profiling<00:05:38.919> of<00:05:39.120> multiple<00:05:39.560> clients<00:05:40.000> at 00:05:40.070 --> 00:05:40.080 align:start position:0% this profiling of multiple clients at 00:05:40.080 --> 00:05:43.950 align:start position:0% this profiling of multiple clients at least<00:05:40.400> do<00:05:41.000> what<00:05:41.160> I<00:05:41.319> focused<00:05:42.120> on<00:05:43.120> uh<00:05:43.319> devop 00:05:43.950 --> 00:05:43.960 align:start position:0% least do what I focused on uh devop 00:05:43.960 --> 00:05:46.749 align:start position:0% least do what I focused on uh devop emphasis<00:05:44.840> I<00:05:45.280> decided<00:05:45.720> to<00:05:45.880> go<00:05:46.120> there<00:05:46.319> since<00:05:46.600> I 00:05:46.749 --> 00:05:46.759 align:start position:0% emphasis I decided to go there since I 00:05:46.759 --> 00:05:48.270 align:start position:0% emphasis I decided to go there since I have<00:05:46.919> no<00:05:47.160> experience<00:05:47.560> doing<00:05:47.759> any<00:05:47.960> sort<00:05:48.160> of 00:05:48.270 --> 00:05:48.280 align:start position:0% have no experience doing any sort of 00:05:48.280 --> 00:05:50.749 align:start position:0% have no experience doing any sort of devops<00:05:48.759> work<00:05:49.039> and<00:05:49.160> I<00:05:49.240> figured<00:05:49.759> having<00:05:50.639> a 00:05:50.749 --> 00:05:50.759 align:start position:0% devops work and I figured having a 00:05:50.759 --> 00:05:52.390 align:start position:0% devops work and I figured having a couple<00:05:51.000> of<00:05:51.120> months<00:05:51.600> seemed<00:05:51.880> like<00:05:52.039> a<00:05:52.120> lot<00:05:52.240> of 00:05:52.390 --> 00:05:52.400 align:start position:0% couple of months seemed like a lot of 00:05:52.400 --> 00:05:55.350 align:start position:0% couple of months seemed like a lot of time<00:05:52.960> here<00:05:53.240> that's<00:05:53.360> a<00:05:53.520> good<00:05:53.960> thing<00:05:54.080> to<00:05:54.280> pick<00:05:54.479> up 00:05:55.350 --> 00:05:55.360 align:start position:0% time here that's a good thing to pick up 00:05:55.360 --> 00:05:58.070 align:start position:0% time here that's a good thing to pick up so<00:05:55.560> that<00:05:55.680> was<00:05:55.880> fun<00:05:56.440> uh<00:05:56.600> build<00:05:56.960> my<00:05:57.479> own<00:05:57.720> server 00:05:58.070 --> 00:05:58.080 align:start position:0% so that was fun uh build my own server 00:05:58.080 --> 00:06:00.029 align:start position:0% so that was fun uh build my own server from<00:05:58.319> secondhand<00:05:58.800> part<00:05:59.440> first<00:05:59.680> first<00:05:59.880> time 00:06:00.029 --> 00:06:00.039 align:start position:0% from secondhand part first first time 00:06:00.039 --> 00:06:03.230 align:start position:0% from secondhand part first first time doing<00:06:00.360> that<00:06:00.880> running<00:06:01.280> proxmox<00:06:02.280> um<00:06:02.960> pretty 00:06:03.230 --> 00:06:03.240 align:start position:0% doing that running proxmox um pretty 00:06:03.240 --> 00:06:05.870 align:start position:0% doing that running proxmox um pretty interesting<00:06:03.680> experience<00:06:04.479> uh<00:06:04.600> learned<00:06:04.880> a<00:06:05.039> lot 00:06:05.870 --> 00:06:05.880 align:start position:0% interesting experience uh learned a lot 00:06:05.880 --> 00:06:07.589 align:start position:0% interesting experience uh learned a lot challenges<00:06:06.479> Hardware<00:06:06.880> constraints<00:06:07.400> I 00:06:07.589 --> 00:06:07.599 align:start position:0% challenges Hardware constraints I 00:06:07.599 --> 00:06:09.230 align:start position:0% challenges Hardware constraints I thought<00:06:07.759> I<00:06:07.960> had<00:06:08.240> sufficient<00:06:08.720> amount<00:06:09.080> but 00:06:09.230 --> 00:06:09.240 align:start position:0% thought I had sufficient amount but 00:06:09.240 --> 00:06:11.430 align:start position:0% thought I had sufficient amount but turned<00:06:09.560> out<00:06:09.919> that<00:06:10.479> maybe<00:06:10.800> the<00:06:11.000> minimal 00:06:11.430 --> 00:06:11.440 align:start position:0% turned out that maybe the minimal 00:06:11.440 --> 00:06:14.430 align:start position:0% turned out that maybe the minimal required<00:06:11.840> specs<00:06:12.599> listed<00:06:13.319> are<00:06:13.520> not<00:06:13.919> entirely 00:06:14.430 --> 00:06:14.440 align:start position:0% required specs listed are not entirely 00:06:14.440 --> 00:06:16.950 align:start position:0% required specs listed are not entirely enough<00:06:14.720> to<00:06:14.919> run<00:06:15.319> all<00:06:15.599> the<00:06:15.720> notes<00:06:16.039> on<00:06:16.199> a<00:06:16.360> single 00:06:16.950 --> 00:06:16.960 align:start position:0% enough to run all the notes on a single 00:06:16.960 --> 00:06:19.070 align:start position:0% enough to run all the notes on a single uh<00:06:17.080> server<00:06:17.960> at<00:06:18.080> least<00:06:18.240> not<00:06:18.400> the<00:06:18.479> one<00:06:18.680> that<00:06:18.840> I 00:06:19.070 --> 00:06:19.080 align:start position:0% uh server at least not the one that I 00:06:19.080 --> 00:06:22.029 align:start position:0% uh server at least not the one that I decided<00:06:19.440> to<00:06:19.880> assemble<00:06:20.880> um<00:06:21.199> and<00:06:21.560> regarding<00:06:21.919> the 00:06:22.029 --> 00:06:22.039 align:start position:0% decided to assemble um and regarding the 00:06:22.039 --> 00:06:23.909 align:start position:0% decided to assemble um and regarding the outcome<00:06:22.560> yeah<00:06:22.680> well<00:06:22.800> there's<00:06:23.039> limited<00:06:23.360> data 00:06:23.909 --> 00:06:23.919 align:start position:0% outcome yeah well there's limited data 00:06:23.919 --> 00:06:26.710 align:start position:0% outcome yeah well there's limited data uh<00:06:24.039> the<00:06:24.280> results<00:06:24.599> are<00:06:25.160> modest<00:06:26.000> but<00:06:26.319> valuable 00:06:26.710 --> 00:06:26.720 align:start position:0% uh the results are modest but valuable 00:06:26.720 --> 00:06:29.150 align:start position:0% uh the results are modest but valuable insight<00:06:27.120> into<00:06:27.479> running<00:06:27.919> ethereum<00:06:28.319> notes<00:06:28.880> was 00:06:29.150 --> 00:06:29.160 align:start position:0% insight into running ethereum notes was 00:06:29.160 --> 00:06:32.230 align:start position:0% insight into running ethereum notes was acquired 00:06:32.230 --> 00:06:32.240 align:start position:0% 00:06:32.240 --> 00:06:34.110 align:start position:0% so<00:06:32.400> let<00:06:32.520> me<00:06:32.639> tell<00:06:32.759> you<00:06:32.880> a<00:06:33.000> bit<00:06:33.160> about<00:06:33.479> the<00:06:33.720> setup 00:06:34.110 --> 00:06:34.120 align:start position:0% so let me tell you a bit about the setup 00:06:34.120 --> 00:06:37.230 align:start position:0% so let me tell you a bit about the setup that<00:06:34.199> I<00:06:34.319> used<00:06:35.280> so<00:06:35.440> I<00:06:35.599> listed<00:06:35.960> on<00:06:36.160> the<00:06:36.880> left<00:06:37.080> side 00:06:37.230 --> 00:06:37.240 align:start position:0% that I used so I listed on the left side 00:06:37.240 --> 00:06:38.790 align:start position:0% that I used so I listed on the left side for<00:06:37.360> you<00:06:37.560> guys<00:06:37.800> the<00:06:37.960> consensus<00:06:38.360> clients<00:06:38.720> that 00:06:38.790 --> 00:06:38.800 align:start position:0% for you guys the consensus clients that 00:06:38.800 --> 00:06:40.309 align:start position:0% for you guys the consensus clients that are<00:06:39.000> there<00:06:39.160> and<00:06:39.280> the<00:06:39.440> versions<00:06:39.800> of<00:06:40.000> those<00:06:40.199> that 00:06:40.309 --> 00:06:40.319 align:start position:0% are there and the versions of those that 00:06:40.319 --> 00:06:42.510 align:start position:0% are there and the versions of those that I<00:06:40.400> used<00:06:40.960> two<00:06:41.160> of<00:06:41.319> them<00:06:41.720> don't<00:06:41.960> have<00:06:42.080> a<00:06:42.199> version 00:06:42.510 --> 00:06:42.520 align:start position:0% I used two of them don't have a version 00:06:42.520 --> 00:06:43.990 align:start position:0% I used two of them don't have a version specified<00:06:43.120> and<00:06:43.199> that's<00:06:43.440> because<00:06:43.639> I<00:06:43.759> didn't 00:06:43.990 --> 00:06:44.000 align:start position:0% specified and that's because I didn't 00:06:44.000 --> 00:06:46.430 align:start position:0% specified and that's because I didn't manage<00:06:44.240> to<00:06:44.440> run<00:06:44.880> run<00:06:45.160> them<00:06:45.720> so<00:06:45.919> they<00:06:46.039> were<00:06:46.240> not 00:06:46.430 --> 00:06:46.440 align:start position:0% manage to run run them so they were not 00:06:46.440 --> 00:06:48.350 align:start position:0% manage to run run them so they were not included<00:06:47.080> I<00:06:47.199> would<00:06:47.360> like<00:06:47.479> to<00:06:47.639> include<00:06:48.039> them<00:06:48.280> at 00:06:48.350 --> 00:06:48.360 align:start position:0% included I would like to include them at 00:06:48.360 --> 00:06:50.629 align:start position:0% included I would like to include them at a<00:06:48.479> later<00:06:48.800> stage<00:06:49.280> when<00:06:49.440> I<00:06:49.599> have<00:06:50.080> the<00:06:50.240> capacity 00:06:50.629 --> 00:06:50.639 align:start position:0% a later stage when I have the capacity 00:06:50.639 --> 00:06:54.390 align:start position:0% a later stage when I have the capacity to<00:06:50.800> do<00:06:51.240> so<00:06:52.240> in<00:06:52.400> terms<00:06:52.639> of<00:06:52.800> Hardware<00:06:53.800> uh<00:06:54.039> I<00:06:54.160> have 00:06:54.390 --> 00:06:54.400 align:start position:0% to do so in terms of Hardware uh I have 00:06:54.400 --> 00:06:56.909 align:start position:0% to do so in terms of Hardware uh I have dedicated<00:06:55.240> uh<00:06:55.360> eight<00:06:55.639> cores<00:06:56.160> to<00:06:56.440> each<00:06:56.680> of 00:06:56.909 --> 00:06:56.919 align:start position:0% dedicated uh eight cores to each of 00:06:56.919 --> 00:07:00.950 align:start position:0% dedicated uh eight cores to each of these<00:06:57.759> um<00:06:58.120> Ram<00:06:58.520> 32<00:06:59.000> GB<00:06:59.759> and<00:06:59.919> the<00:07:00.080> dis<00:07:00.360> space<00:07:00.720> was 00:07:00.950 --> 00:07:00.960 align:start position:0% these um Ram 32 GB and the dis space was 00:07:00.960 --> 00:07:03.629 align:start position:0% these um Ram 32 GB and the dis space was two<00:07:01.240> terabytes<00:07:01.840> and<00:07:02.000> VM<00:07:02.440> Drive<00:07:03.280> which<00:07:03.440> is 00:07:03.629 --> 00:07:03.639 align:start position:0% two terabytes and VM Drive which is 00:07:03.639 --> 00:07:05.230 align:start position:0% two terabytes and VM Drive which is sufficient<00:07:04.120> for<00:07:04.319> all<00:07:04.479> these<00:07:04.639> clients<00:07:04.919> to<00:07:05.080> not 00:07:05.230 --> 00:07:05.240 align:start position:0% sufficient for all these clients to not 00:07:05.240 --> 00:07:08.070 align:start position:0% sufficient for all these clients to not be<00:07:05.479> limited<00:07:06.039> there<00:07:07.039> in<00:07:07.160> the<00:07:07.280> setup<00:07:07.800> I<00:07:07.919> make 00:07:08.070 --> 00:07:08.080 align:start position:0% be limited there in the setup I make 00:07:08.080 --> 00:07:09.790 align:start position:0% be limited there in the setup I make sure<00:07:08.400> that<00:07:08.639> each<00:07:08.879> of<00:07:09.080> them<00:07:09.280> running<00:07:09.560> on<00:07:09.680> a 00:07:09.790 --> 00:07:09.800 align:start position:0% sure that each of them running on a 00:07:09.800 --> 00:07:12.309 align:start position:0% sure that each of them running on a virtual<00:07:10.120> machine<00:07:10.680> is<00:07:10.879> also<00:07:11.639> is<00:07:11.840> limited<00:07:12.160> to 00:07:12.309 --> 00:07:12.319 align:start position:0% virtual machine is also is limited to 00:07:12.319 --> 00:07:15.309 align:start position:0% virtual machine is also is limited to this<00:07:12.599> basically<00:07:13.160> so<00:07:13.319> there's<00:07:13.560> no<00:07:13.800> way<00:07:14.120> that<00:07:15.120> if 00:07:15.309 --> 00:07:15.319 align:start position:0% this basically so there's no way that if 00:07:15.319 --> 00:07:17.950 align:start position:0% this basically so there's no way that if one<00:07:15.479> of<00:07:15.639> the<00:07:15.759> VMS<00:07:16.199> isn't<00:07:16.520> using<00:07:17.000> all<00:07:17.160> of<00:07:17.360> its 00:07:17.950 --> 00:07:17.960 align:start position:0% one of the VMS isn't using all of its 00:07:17.960 --> 00:07:20.189 align:start position:0% one of the VMS isn't using all of its Ram<00:07:18.360> that<00:07:18.560> one<00:07:18.680> of<00:07:18.800> the<00:07:18.919> others<00:07:19.280> could<00:07:19.840> uh<00:07:19.960> use 00:07:20.189 --> 00:07:20.199 align:start position:0% Ram that one of the others could uh use 00:07:20.199 --> 00:07:22.150 align:start position:0% Ram that one of the others could uh use it<00:07:20.840> because<00:07:21.039> it's<00:07:21.240> available<00:07:21.919> this<00:07:22.000> is 00:07:22.150 --> 00:07:22.160 align:start position:0% it because it's available this is 00:07:22.160 --> 00:07:23.909 align:start position:0% it because it's available this is normally<00:07:22.479> something<00:07:22.720> that<00:07:22.879> Pro<00:07:23.160> Mo<00:07:23.400> supports 00:07:23.909 --> 00:07:23.919 align:start position:0% normally something that Pro Mo supports 00:07:23.919 --> 00:07:25.990 align:start position:0% normally something that Pro Mo supports but<00:07:24.120> that<00:07:24.360> of<00:07:24.520> course<00:07:25.240> doesn't<00:07:25.560> allow<00:07:25.759> for<00:07:25.919> a 00:07:25.990 --> 00:07:26.000 align:start position:0% but that of course doesn't allow for a 00:07:26.000 --> 00:07:28.510 align:start position:0% but that of course doesn't allow for a proper<00:07:26.280> comparative<00:07:26.879> analysis<00:07:27.879> um<00:07:28.080> then<00:07:28.319> the 00:07:28.510 --> 00:07:28.520 align:start position:0% proper comparative analysis um then the 00:07:28.520 --> 00:07:30.710 align:start position:0% proper comparative analysis um then the services<00:07:29.160> that<00:07:29.319> I<00:07:29.759> also<00:07:29.960> got<00:07:30.120> to<00:07:30.280> work<00:07:30.520> with 00:07:30.710 --> 00:07:30.720 align:start position:0% services that I also got to work with 00:07:30.720 --> 00:07:32.430 align:start position:0% services that I also got to work with and<00:07:30.840> got<00:07:31.000> to<00:07:31.120> learn<00:07:31.400> about<00:07:31.680> and<00:07:31.800> nethermind<00:07:32.319> of 00:07:32.430 --> 00:07:32.440 align:start position:0% and got to learn about and nethermind of 00:07:32.440 --> 00:07:34.189 align:start position:0% and got to learn about and nethermind of course<00:07:32.599> I<00:07:32.680> need<00:07:32.840> an<00:07:33.000> execution<00:07:33.479> client<00:07:34.000> and<00:07:34.120> a 00:07:34.189 --> 00:07:34.199 align:start position:0% course I need an execution client and a 00:07:34.199 --> 00:07:35.469 align:start position:0% course I need an execution client and a whole<00:07:34.360> bunch<00:07:34.520> of<00:07:34.639> other<00:07:34.840> services<00:07:35.280> that 00:07:35.469 --> 00:07:35.479 align:start position:0% whole bunch of other services that 00:07:35.479 --> 00:07:37.469 align:start position:0% whole bunch of other services that anybody<00:07:35.800> who's<00:07:36.039> done<00:07:36.199> anything<00:07:36.440> in<00:07:36.599> devops 00:07:37.469 --> 00:07:37.479 align:start position:0% anybody who's done anything in devops 00:07:37.479 --> 00:07:40.230 align:start position:0% anybody who's done anything in devops probably<00:07:37.720> knows<00:07:38.440> so<00:07:38.720> Prometheus<00:07:39.400> obviously 00:07:40.230 --> 00:07:40.240 align:start position:0% probably knows so Prometheus obviously 00:07:40.240 --> 00:07:42.990 align:start position:0% probably knows so Prometheus obviously for<00:07:40.680> metrics<00:07:41.680> um<00:07:42.160> I'm<00:07:42.280> not<00:07:42.400> going<00:07:42.520> to<00:07:42.639> mention 00:07:42.990 --> 00:07:43.000 align:start position:0% for metrics um I'm not going to mention 00:07:43.000 --> 00:07:44.510 align:start position:0% for metrics um I'm not going to mention them<00:07:43.160> all<00:07:43.440> but<00:07:43.639> I<00:07:43.720> will<00:07:43.879> just<00:07:44.039> say<00:07:44.240> that<00:07:44.360> these 00:07:44.510 --> 00:07:44.520 align:start position:0% them all but I will just say that these 00:07:44.520 --> 00:07:47.710 align:start position:0% them all but I will just say that these were<00:07:44.680> a<00:07:44.759> lot<00:07:44.879> of<00:07:44.960> tools<00:07:45.360> that<00:07:45.560> were<00:07:46.240> new<00:07:46.520> to<00:07:46.639> me 00:07:47.710 --> 00:07:47.720 align:start position:0% were a lot of tools that were new to me 00:07:47.720 --> 00:07:49.950 align:start position:0% were a lot of tools that were new to me um<00:07:48.720> quite<00:07:48.960> interesting<00:07:49.319> to<00:07:49.440> see<00:07:49.639> how<00:07:49.759> many 00:07:49.950 --> 00:07:49.960 align:start position:0% um quite interesting to see how many 00:07:49.960 --> 00:07:52.710 align:start position:0% um quite interesting to see how many services<00:07:50.400> you<00:07:50.639> actually<00:07:50.919> need<00:07:51.240> to<00:07:51.440> run<00:07:51.759> such<00:07:51.960> a 00:07:52.710 --> 00:07:52.720 align:start position:0% services you actually need to run such a 00:07:52.720 --> 00:07:55.469 align:start position:0% services you actually need to run such a such<00:07:52.879> a<00:07:53.000> node<00:07:53.319> and<00:07:53.560> a<00:07:54.319> in<00:07:54.440> a<00:07:54.599> useful<00:07:55.039> way<00:07:55.319> so 00:07:55.469 --> 00:07:55.479 align:start position:0% such a node and a in a useful way so 00:07:55.479 --> 00:07:56.710 align:start position:0% such a node and a in a useful way so that<00:07:55.599> you<00:07:55.759> actually<00:07:55.960> can<00:07:56.120> monitor<00:07:56.479> what's 00:07:56.710 --> 00:07:56.720 align:start position:0% that you actually can monitor what's 00:07:56.720 --> 00:07:57.430 align:start position:0% that you actually can monitor what's going 00:07:57.430 --> 00:07:57.440 align:start position:0% going 00:07:57.440 --> 00:07:59.909 align:start position:0% going on<00:07:58.440> then<00:07:58.599> I'm<00:07:58.759> going<00:07:58.840> to<00:07:58.960> show<00:07:59.120> a<00:07:59.199> couple 00:07:59.909 --> 00:07:59.919 align:start position:0% on then I'm going to show a couple 00:07:59.919 --> 00:08:02.749 align:start position:0% on then I'm going to show a couple figures<00:08:00.919> on<00:08:01.120> some<00:08:01.280> of<00:08:01.400> the<00:08:01.599> data<00:08:01.919> it's<00:08:02.080> a<00:08:02.240> bit 00:08:02.749 --> 00:08:02.759 align:start position:0% figures on some of the data it's a bit 00:08:02.759 --> 00:08:06.309 align:start position:0% figures on some of the data it's a bit older<00:08:03.360> data<00:08:04.000> but<00:08:04.440> uh<00:08:04.560> so<00:08:04.800> be<00:08:05.000> it<00:08:05.599> so<00:08:05.919> this<00:08:06.080> is 00:08:06.309 --> 00:08:06.319 align:start position:0% older data but uh so be it so this is 00:08:06.319 --> 00:08:08.230 align:start position:0% older data but uh so be it so this is the<00:08:06.440> CPU<00:08:06.879> usage<00:08:07.199> that<00:08:07.360> I<00:08:07.520> measured<00:08:07.919> over<00:08:08.120> the 00:08:08.230 --> 00:08:08.240 align:start position:0% the CPU usage that I measured over the 00:08:08.240 --> 00:08:11.149 align:start position:0% the CPU usage that I measured over the course<00:08:08.520> of<00:08:09.080> About<00:08:09.280> a<00:08:09.400> Week<00:08:09.639> a<00:08:09.759> little<00:08:10.159> longer 00:08:11.149 --> 00:08:11.159 align:start position:0% course of About a Week a little longer 00:08:11.159 --> 00:08:12.469 align:start position:0% course of About a Week a little longer uh<00:08:11.240> for<00:08:11.440> four<00:08:11.639> of<00:08:11.720> the<00:08:11.800> consensus<00:08:12.199> clients 00:08:12.469 --> 00:08:12.479 align:start position:0% uh for four of the consensus clients 00:08:12.479 --> 00:08:14.629 align:start position:0% uh for four of the consensus clients that<00:08:12.560> I<00:08:12.919> mentioned<00:08:13.919> and<00:08:14.039> now<00:08:14.199> the<00:08:14.360> question 00:08:14.629 --> 00:08:14.639 align:start position:0% that I mentioned and now the question 00:08:14.639 --> 00:08:16.629 align:start position:0% that I mentioned and now the question obviously<00:08:15.080> is<00:08:15.280> what<00:08:15.479> does<00:08:15.680> this<00:08:15.840> mean<00:08:16.240> and<00:08:16.479> I 00:08:16.629 --> 00:08:16.639 align:start position:0% obviously is what does this mean and I 00:08:16.639 --> 00:08:18.469 align:start position:0% obviously is what does this mean and I don't<00:08:16.919> have<00:08:17.080> a<00:08:17.240> crystal<00:08:17.560> clear<00:08:17.759> answer<00:08:18.000> to<00:08:18.120> you 00:08:18.469 --> 00:08:18.479 align:start position:0% don't have a crystal clear answer to you 00:08:18.479 --> 00:08:19.950 align:start position:0% don't have a crystal clear answer to you I<00:08:18.599> do<00:08:18.840> notice<00:08:19.159> some<00:08:19.319> things<00:08:19.599> which<00:08:19.720> you'll 00:08:19.950 --> 00:08:19.960 align:start position:0% I do notice some things which you'll 00:08:19.960 --> 00:08:21.350 align:start position:0% I do notice some things which you'll probably<00:08:20.240> also<00:08:20.479> notice<00:08:20.800> straight<00:08:21.080> away<00:08:21.240> which 00:08:21.350 --> 00:08:21.360 align:start position:0% probably also notice straight away which 00:08:21.360 --> 00:08:23.710 align:start position:0% probably also notice straight away which is<00:08:21.440> that<00:08:21.599> grandine<00:08:22.039> seems<00:08:22.960> on<00:08:23.120> the<00:08:23.280> average<00:08:23.599> to 00:08:23.710 --> 00:08:23.720 align:start position:0% is that grandine seems on the average to 00:08:23.720 --> 00:08:26.749 align:start position:0% is that grandine seems on the average to have<00:08:23.879> the<00:08:23.960> lowest<00:08:24.639> CPU<00:08:25.240> usage<00:08:26.240> but<00:08:26.520> there<00:08:26.599> is 00:08:26.749 --> 00:08:26.759 align:start position:0% have the lowest CPU usage but there is 00:08:26.759 --> 00:08:29.029 align:start position:0% have the lowest CPU usage but there is somewhere<00:08:27.039> a<00:08:27.240> spike<00:08:27.520> in<00:08:27.599> the<00:08:27.720> middle<00:08:28.560> um<00:08:28.759> I<00:08:28.840> see 00:08:29.029 --> 00:08:29.039 align:start position:0% somewhere a spike in the middle um I see 00:08:29.039 --> 00:08:30.589 align:start position:0% somewhere a spike in the middle um I see that<00:08:29.159> in<00:08:29.240> a<00:08:29.520> data<00:08:29.720> figure<00:08:29.960> in<00:08:30.039> the<00:08:30.159> next<00:08:30.360> figure 00:08:30.589 --> 00:08:30.599 align:start position:0% that in a data figure in the next figure 00:08:30.599 --> 00:08:32.870 align:start position:0% that in a data figure in the next figure I'll<00:08:30.759> show<00:08:31.039> as<00:08:31.159> well<00:08:31.879> and<00:08:32.120> honestly<00:08:32.680> I'm 00:08:32.870 --> 00:08:32.880 align:start position:0% I'll show as well and honestly I'm 00:08:32.880 --> 00:08:34.990 align:start position:0% I'll show as well and honestly I'm curious<00:08:33.360> what<00:08:33.599> happened<00:08:33.959> there<00:08:34.360> but<00:08:34.560> I<00:08:34.680> simply 00:08:34.990 --> 00:08:35.000 align:start position:0% curious what happened there but I simply 00:08:35.000 --> 00:08:36.870 align:start position:0% curious what happened there but I simply don't<00:08:35.159> know<00:08:35.560> I<00:08:35.719> probably<00:08:35.959> need<00:08:36.159> more<00:08:36.399> data 00:08:36.870 --> 00:08:36.880 align:start position:0% don't know I probably need more data 00:08:36.880 --> 00:08:39.310 align:start position:0% don't know I probably need more data from<00:08:37.039> the<00:08:37.159> metrics<00:08:37.599> alone<00:08:38.599> it's<00:08:38.760> not<00:08:38.919> so<00:08:39.080> clear 00:08:39.310 --> 00:08:39.320 align:start position:0% from the metrics alone it's not so clear 00:08:39.320 --> 00:08:42.029 align:start position:0% from the metrics alone it's not so clear it<00:08:39.440> could<00:08:39.839> be<00:08:40.839> various<00:08:41.240> things<00:08:41.479> it<00:08:41.640> might<00:08:41.839> be 00:08:42.029 --> 00:08:42.039 align:start position:0% it could be various things it might be 00:08:42.039 --> 00:08:43.469 align:start position:0% it could be various things it might be something<00:08:42.320> Network<00:08:42.719> related<00:08:43.200> could<00:08:43.360> be 00:08:43.469 --> 00:08:43.479 align:start position:0% something Network related could be 00:08:43.479 --> 00:08:45.670 align:start position:0% something Network related could be something<00:08:43.719> client<00:08:44.160> specific<00:08:45.160> simply<00:08:45.519> don't 00:08:45.670 --> 00:08:45.680 align:start position:0% something client specific simply don't 00:08:45.680 --> 00:08:47.670 align:start position:0% something client specific simply don't have<00:08:45.800> an<00:08:45.920> answer<00:08:46.120> for<00:08:46.279> you<00:08:46.519> there<00:08:47.399> here<00:08:47.560> I 00:08:47.670 --> 00:08:47.680 align:start position:0% have an answer for you there here I 00:08:47.680 --> 00:08:49.110 align:start position:0% have an answer for you there here I looked<00:08:47.920> at<00:08:48.040> the<00:08:48.160> memory<00:08:48.440> usage<00:08:48.880> of<00:08:49.000> the 00:08:49.110 --> 00:08:49.120 align:start position:0% looked at the memory usage of the 00:08:49.120 --> 00:08:49.910 align:start position:0% looked at the memory usage of the different 00:08:49.910 --> 00:08:49.920 align:start position:0% different 00:08:49.920 --> 00:08:53.509 align:start position:0% different clients<00:08:51.000> um<00:08:52.000> also<00:08:52.440> you<00:08:52.560> see<00:08:52.760> the<00:08:52.920> same<00:08:53.160> spike 00:08:53.509 --> 00:08:53.519 align:start position:0% clients um also you see the same spike 00:08:53.519 --> 00:08:54.949 align:start position:0% clients um also you see the same spike in<00:08:53.640> the<00:08:53.760> same<00:08:53.959> period<00:08:54.279> but<00:08:54.399> it's<00:08:54.560> for<00:08:54.800> a 00:08:54.949 --> 00:08:54.959 align:start position:0% in the same period but it's for a 00:08:54.959 --> 00:08:56.190 align:start position:0% in the same period but it's for a different 00:08:56.190 --> 00:08:56.200 align:start position:0% different 00:08:56.200 --> 00:08:58.350 align:start position:0% different client<00:08:57.200> so<00:08:57.519> yeah<00:08:57.680> there's<00:08:57.959> definitely 00:08:58.350 --> 00:08:58.360 align:start position:0% client so yeah there's definitely 00:08:58.360 --> 00:09:00.150 align:start position:0% client so yeah there's definitely something<00:08:58.680> going<00:08:58.880> on<00:08:59.120> there<00:08:59.320> and<00:08:59.519> and<00:08:59.800> I<00:08:59.880> would 00:09:00.150 --> 00:09:00.160 align:start position:0% something going on there and and I would 00:09:00.160 --> 00:09:02.750 align:start position:0% something going on there and and I would say<00:09:00.519> that<00:09:01.040> my<00:09:01.399> suspicion<00:09:01.839> is<00:09:02.000> that<00:09:02.160> it<00:09:02.399> has 00:09:02.750 --> 00:09:02.760 align:start position:0% say that my suspicion is that it has 00:09:02.760 --> 00:09:04.110 align:start position:0% say that my suspicion is that it has something<00:09:03.000> to<00:09:03.120> do<00:09:03.279> with<00:09:03.399> my<00:09:03.519> server<00:09:03.839> at<00:09:03.959> that 00:09:04.110 --> 00:09:04.120 align:start position:0% something to do with my server at that 00:09:04.120 --> 00:09:06.870 align:start position:0% something to do with my server at that point<00:09:04.320> since<00:09:04.480> I<00:09:04.560> see<00:09:04.760> this<00:09:04.920> weird<00:09:05.640> pattern<00:09:06.640> but 00:09:06.870 --> 00:09:06.880 align:start position:0% point since I see this weird pattern but 00:09:06.880 --> 00:09:08.829 align:start position:0% point since I see this weird pattern but like<00:09:07.040> I<00:09:07.160> said<00:09:07.440> I<00:09:07.600> have<00:09:07.760> no<00:09:08.240> straight<00:09:08.560> answers 00:09:08.829 --> 00:09:08.839 align:start position:0% like I said I have no straight answers 00:09:08.839 --> 00:09:13.670 align:start position:0% like I said I have no straight answers for<00:09:09.160> you<00:09:10.160> and<00:09:10.320> then<00:09:10.480> the<00:09:10.680> last<00:09:10.880> figure 00:09:13.670 --> 00:09:13.680 align:start position:0% 00:09:13.680 --> 00:09:17.750 align:start position:0% I<00:09:15.040> will<00:09:16.040> show<00:09:16.800> I<00:09:16.880> think<00:09:17.040> this<00:09:17.160> is<00:09:17.360> actually<00:09:17.640> one 00:09:17.750 --> 00:09:17.760 align:start position:0% I will show I think this is actually one 00:09:17.760 --> 00:09:19.870 align:start position:0% I will show I think this is actually one of<00:09:17.880> the<00:09:18.040> things<00:09:18.279> that<00:09:18.440> is<00:09:18.640> highly<00:09:18.920> relevant<00:09:19.800> I 00:09:19.870 --> 00:09:19.880 align:start position:0% of the things that is highly relevant I 00:09:19.880 --> 00:09:21.670 align:start position:0% of the things that is highly relevant I only<00:09:20.079> show<00:09:20.399> grandine<00:09:20.839> and<00:09:21.040> Lighthouse<00:09:21.480> here 00:09:21.670 --> 00:09:21.680 align:start position:0% only show grandine and Lighthouse here 00:09:21.680 --> 00:09:23.269 align:start position:0% only show grandine and Lighthouse here because<00:09:22.000> the<00:09:22.120> initial<00:09:22.440> Focus<00:09:22.760> was<00:09:22.920> more<00:09:23.040> or 00:09:23.269 --> 00:09:23.279 align:start position:0% because the initial Focus was more or 00:09:23.279 --> 00:09:26.630 align:start position:0% because the initial Focus was more or less<00:09:24.279> on<00:09:24.480> grandine<00:09:25.040> and<00:09:25.720> well<00:09:25.880> for<00:09:26.079> comparison 00:09:26.630 --> 00:09:26.640 align:start position:0% less on grandine and well for comparison 00:09:26.640 --> 00:09:28.069 align:start position:0% less on grandine and well for comparison also<00:09:26.920> taking<00:09:27.240> into<00:09:27.480> consideration 00:09:28.069 --> 00:09:28.079 align:start position:0% also taking into consideration 00:09:28.079 --> 00:09:29.949 align:start position:0% also taking into consideration Lighthouse<00:09:28.880> so<00:09:29.120> the<00:09:29.399> number<00:09:29.560> of<00:09:29.640> pairs<00:09:29.880> that 00:09:29.949 --> 00:09:29.959 align:start position:0% Lighthouse so the number of pairs that 00:09:29.959 --> 00:09:32.430 align:start position:0% Lighthouse so the number of pairs that you<00:09:30.079> have<00:09:30.240> is<00:09:30.440> obviously<00:09:30.920> very<00:09:31.360> important<00:09:32.360> uh 00:09:32.430 --> 00:09:32.440 align:start position:0% you have is obviously very important uh 00:09:32.440 --> 00:09:33.670 align:start position:0% you have is obviously very important uh and<00:09:32.519> you<00:09:32.640> can<00:09:32.760> see<00:09:32.959> that<00:09:33.079> there<00:09:33.160> are<00:09:33.399> actually 00:09:33.670 --> 00:09:33.680 align:start position:0% and you can see that there are actually 00:09:33.680 --> 00:09:35.790 align:start position:0% and you can see that there are actually quite<00:09:33.920> large<00:09:34.200> spikes<00:09:34.600> to<00:09:34.959> the<00:09:35.120> downside<00:09:35.720> I 00:09:35.790 --> 00:09:35.800 align:start position:0% quite large spikes to the downside I 00:09:35.800 --> 00:09:37.910 align:start position:0% quite large spikes to the downside I have<00:09:35.920> the<00:09:36.040> limit<00:09:36.279> set<00:09:36.480> at<00:09:36.760> 100<00:09:37.399> so<00:09:37.600> that's<00:09:37.800> why 00:09:37.910 --> 00:09:37.920 align:start position:0% have the limit set at 100 so that's why 00:09:37.920 --> 00:09:41.110 align:start position:0% have the limit set at 100 so that's why it<00:09:38.040> looks<00:09:39.000> kind<00:09:39.079> of<00:09:39.240> artificially<00:09:39.839> kept<00:09:40.200> there 00:09:41.110 --> 00:09:41.120 align:start position:0% it looks kind of artificially kept there 00:09:41.120 --> 00:09:42.829 align:start position:0% it looks kind of artificially kept there um<00:09:41.480> but<00:09:41.640> yeah<00:09:41.760> if<00:09:41.800> you<00:09:41.920> lose<00:09:42.120> a<00:09:42.200> lot<00:09:42.360> of<00:09:42.480> pairs 00:09:42.829 --> 00:09:42.839 align:start position:0% um but yeah if you lose a lot of pairs 00:09:42.839 --> 00:09:44.870 align:start position:0% um but yeah if you lose a lot of pairs that's<00:09:43.079> obviously<00:09:43.440> not<00:09:43.600> a<00:09:43.720> good<00:09:43.880> sign<00:09:44.279> and 00:09:44.870 --> 00:09:44.880 align:start position:0% that's obviously not a good sign and 00:09:44.880 --> 00:09:47.430 align:start position:0% that's obviously not a good sign and well<00:09:45.160> this<00:09:45.440> seems<00:09:45.720> to<00:09:45.880> be 00:09:47.430 --> 00:09:47.440 align:start position:0% well this seems to be 00:09:47.440 --> 00:09:50.750 align:start position:0% well this seems to be fairly<00:09:48.440> maybe<00:09:48.680> not<00:09:48.839> stable<00:09:49.240> enough<00:09:50.240> um<00:09:50.360> or<00:09:50.560> not 00:09:50.750 --> 00:09:50.760 align:start position:0% fairly maybe not stable enough um or not 00:09:50.760 --> 00:09:52.509 align:start position:0% fairly maybe not stable enough um or not as<00:09:50.880> stable<00:09:51.160> as<00:09:51.279> you<00:09:51.399> might<00:09:51.600> want<00:09:51.760> it<00:09:52.240> so<00:09:52.399> in 00:09:52.509 --> 00:09:52.519 align:start position:0% as stable as you might want it so in 00:09:52.519 --> 00:09:53.550 align:start position:0% as stable as you might want it so in terms<00:09:52.720> of 00:09:53.550 --> 00:09:53.560 align:start position:0% terms of 00:09:53.560 --> 00:09:55.710 align:start position:0% terms of Outlook<00:09:54.560> what<00:09:54.680> I<00:09:54.760> would<00:09:54.880> like<00:09:55.000> to<00:09:55.120> do<00:09:55.320> is 00:09:55.710 --> 00:09:55.720 align:start position:0% Outlook what I would like to do is 00:09:55.720 --> 00:09:57.590 align:start position:0% Outlook what I would like to do is refine<00:09:56.079> and<00:09:56.240> scale<00:09:56.560> this<00:09:56.720> node<00:09:57.000> management<00:09:57.480> so 00:09:57.590 --> 00:09:57.600 align:start position:0% refine and scale this node management so 00:09:57.600 --> 00:10:00.190 align:start position:0% refine and scale this node management so I<00:09:57.760> now<00:09:58.200> have<00:09:58.600> almost<00:09:59.360> automated<00:09:59.720> setup<00:09:59.959> for 00:10:00.190 --> 00:10:00.200 align:start position:0% I now have almost automated setup for 00:10:00.200 --> 00:10:02.910 align:start position:0% I now have almost automated setup for the<00:10:00.440> provisioning<00:10:00.959> of<00:10:01.120> my<00:10:01.480> VMS<00:10:02.480> I<00:10:02.560> would<00:10:02.720> still 00:10:02.910 --> 00:10:02.920 align:start position:0% the provisioning of my VMS I would still 00:10:02.920 --> 00:10:05.389 align:start position:0% the provisioning of my VMS I would still need<00:10:03.040> to<00:10:03.240> switch<00:10:03.680> to<00:10:03.880> nyos<00:10:04.480> or<00:10:04.640> Taos<00:10:05.160> to<00:10:05.320> have 00:10:05.389 --> 00:10:05.399 align:start position:0% need to switch to nyos or Taos to have 00:10:05.399 --> 00:10:08.829 align:start position:0% need to switch to nyos or Taos to have it<00:10:05.519> fairly<00:10:06.079> immutable<00:10:06.560> and<00:10:06.720> item<00:10:07.120> potent<00:10:08.120> then 00:10:08.829 --> 00:10:08.839 align:start position:0% it fairly immutable and item potent then 00:10:08.839 --> 00:10:10.750 align:start position:0% it fairly immutable and item potent then I<00:10:08.920> want<00:10:09.040> to<00:10:09.160> integrate<00:10:09.560> e<00:10:09.839> Docker<00:10:10.399> this<00:10:10.519> is 00:10:10.750 --> 00:10:10.760 align:start position:0% I want to integrate e Docker this is 00:10:10.760 --> 00:10:12.269 align:start position:0% I want to integrate e Docker this is something<00:10:11.279> that<00:10:11.480> I<00:10:11.560> simply<00:10:11.880> didn't<00:10:12.120> have 00:10:12.269 --> 00:10:12.279 align:start position:0% something that I simply didn't have 00:10:12.279 --> 00:10:14.150 align:start position:0% something that I simply didn't have enough<00:10:12.519> time<00:10:12.680> to<00:10:12.880> properly<00:10:13.240> look<00:10:13.399> into<00:10:13.720> so<00:10:13.959> so 00:10:14.150 --> 00:10:14.160 align:start position:0% enough time to properly look into so so 00:10:14.160 --> 00:10:17.150 align:start position:0% enough time to properly look into so so far<00:10:14.360> what<00:10:14.480> I've<00:10:14.640> been<00:10:14.800> using<00:10:15.079> is<00:10:15.880> sge<00:10:16.880> uh<00:10:17.000> well 00:10:17.150 --> 00:10:17.160 align:start position:0% far what I've been using is sge uh well 00:10:17.160 --> 00:10:19.550 align:start position:0% far what I've been using is sge uh well I<00:10:17.240> started<00:10:17.560> with<00:10:17.680> simple<00:10:18.000> scripts<00:10:18.560> and 00:10:19.550 --> 00:10:19.560 align:start position:0% I started with simple scripts and 00:10:19.560 --> 00:10:21.630 align:start position:0% I started with simple scripts and running<00:10:19.920> local<00:10:20.200> binaries<00:10:20.760> and<00:10:20.959> eventually 00:10:21.630 --> 00:10:21.640 align:start position:0% running local binaries and eventually 00:10:21.640 --> 00:10:24.069 align:start position:0% running local binaries and eventually went<00:10:21.880> on<00:10:22.120> to<00:10:22.399> use<00:10:22.640> Docker<00:10:22.920> compose<00:10:23.600> but<00:10:23.880> yeah<00:10:24.000> I 00:10:24.069 --> 00:10:24.079 align:start position:0% went on to use Docker compose but yeah I 00:10:24.079 --> 00:10:25.910 align:start position:0% went on to use Docker compose but yeah I would<00:10:24.240> like<00:10:24.360> to<00:10:24.760> move<00:10:25.000> to<00:10:25.160> kubernetes<00:10:25.760> and<00:10:25.839> I 00:10:25.910 --> 00:10:25.920 align:start position:0% would like to move to kubernetes and I 00:10:25.920 --> 00:10:28.990 align:start position:0% would like to move to kubernetes and I would<00:10:26.120> like<00:10:26.240> to<00:10:26.959> also<00:10:27.959> explore<00:10:28.320> e<00:10:28.600> Docker 00:10:28.990 --> 00:10:29.000 align:start position:0% would like to also explore e Docker 00:10:29.000 --> 00:10:31.230 align:start position:0% would like to also explore e Docker because<00:10:29.399> I<00:10:29.519> think<00:10:29.720> it<00:10:29.880> hoverers<00:10:30.800> some<00:10:30.959> of<00:10:31.120> the 00:10:31.230 --> 00:10:31.240 align:start position:0% because I think it hoverers some of the 00:10:31.240 --> 00:10:33.990 align:start position:0% because I think it hoverers some of the things<00:10:31.399> that<00:10:31.519> I<00:10:31.600> was<00:10:31.760> lacking<00:10:32.320> or<00:10:32.560> missing<00:10:33.040> in 00:10:33.990 --> 00:10:34.000 align:start position:0% things that I was lacking or missing in 00:10:34.000 --> 00:10:37.470 align:start position:0% things that I was lacking or missing in sge<00:10:35.000> and<00:10:35.200> then<00:10:35.519> I<00:10:35.680> only<00:10:36.079> very<00:10:36.320> recently<00:10:37.040> that 00:10:37.470 --> 00:10:37.480 align:start position:0% sge and then I only very recently that 00:10:37.480 --> 00:10:39.430 align:start position:0% sge and then I only very recently that that<00:10:37.600> is<00:10:37.680> to<00:10:37.839> say<00:10:38.079> yesterday<00:10:38.760> learned<00:10:39.120> about 00:10:39.430 --> 00:10:39.440 align:start position:0% that is to say yesterday learned about 00:10:39.440 --> 00:10:41.790 align:start position:0% that is to say yesterday learned about the<00:10:39.600> secret<00:10:39.959> shared<00:10:40.440> validator<00:10:41.440> um<00:10:41.560> so<00:10:41.680> I'm 00:10:41.790 --> 00:10:41.800 align:start position:0% the secret shared validator um so I'm 00:10:41.800 --> 00:10:43.350 align:start position:0% the secret shared validator um so I'm going<00:10:41.880> to<00:10:42.000> look<00:10:42.200> into<00:10:42.480> this<00:10:43.040> this<00:10:43.160> is 00:10:43.350 --> 00:10:43.360 align:start position:0% going to look into this this is 00:10:43.360 --> 00:10:44.750 align:start position:0% going to look into this this is something<00:10:43.800> in<00:10:43.920> the<00:10:44.079> direction<00:10:44.399> that<00:10:44.519> I<00:10:44.600> was 00:10:44.750 --> 00:10:44.760 align:start position:0% something in the direction that I was 00:10:44.760 --> 00:10:47.430 align:start position:0% something in the direction that I was thinking<00:10:45.079> I<00:10:45.160> want<00:10:45.399> to<00:10:45.519> use<00:10:45.880> this<00:10:46.240> setup<00:10:47.240> I<00:10:47.320> want 00:10:47.430 --> 00:10:47.440 align:start position:0% thinking I want to use this setup I want 00:10:47.440 --> 00:10:49.269 align:start position:0% thinking I want to use this setup I want to<00:10:47.519> use<00:10:47.680> this<00:10:47.800> setup<00:10:48.079> myself<00:10:48.519> with<00:10:48.639> an<00:10:48.800> agentic 00:10:49.269 --> 00:10:49.279 align:start position:0% to use this setup myself with an agentic 00:10:49.279 --> 00:10:51.750 align:start position:0% to use this setup myself with an agentic system<00:10:49.680> because<00:10:49.920> there<00:10:50.160> I<00:10:50.279> have<00:10:50.399> a<00:10:50.760> background 00:10:51.750 --> 00:10:51.760 align:start position:0% system because there I have a background 00:10:51.760 --> 00:10:53.750 align:start position:0% system because there I have a background um<00:10:52.000> so<00:10:52.279> I<00:10:52.360> think<00:10:52.519> it<00:10:52.720> might<00:10:52.959> actually<00:10:53.440> partly 00:10:53.750 --> 00:10:53.760 align:start position:0% um so I think it might actually partly 00:10:53.760 --> 00:10:56.150 align:start position:0% um so I think it might actually partly at<00:10:53.880> least<00:10:54.360> overlap<00:10:55.360> with<00:10:55.519> this<00:10:55.639> secret<00:10:55.880> shared 00:10:56.150 --> 00:10:56.160 align:start position:0% at least overlap with this secret shared 00:10:56.160 --> 00:10:58.150 align:start position:0% at least overlap with this secret shared validator<00:10:56.600> setup<00:10:57.040> because<00:10:57.320> I<00:10:57.399> was<00:10:57.880> thinking 00:10:58.150 --> 00:10:58.160 align:start position:0% validator setup because I was thinking 00:10:58.160 --> 00:11:00.550 align:start position:0% validator setup because I was thinking in<00:10:58.279> that<00:10:58.440> same<00:10:58.639> direction<00:10:59.600> and<00:10:59.760> lastly<00:11:00.320> I<00:11:00.440> want 00:11:00.550 --> 00:11:00.560 align:start position:0% in that same direction and lastly I want 00:11:00.560 --> 00:11:02.190 align:start position:0% in that same direction and lastly I want to<00:11:00.680> optimize<00:11:01.079> the<00:11:01.200> data<00:11:01.399> queries<00:11:01.800> because<00:11:02.040> the 00:11:02.190 --> 00:11:02.200 align:start position:0% to optimize the data queries because the 00:11:02.200 --> 00:11:04.269 align:start position:0% to optimize the data queries because the idea<00:11:02.880> of<00:11:03.040> this<00:11:03.160> agentic<00:11:03.600> system<00:11:03.839> would<00:11:04.000> be<00:11:04.120> to 00:11:04.269 --> 00:11:04.279 align:start position:0% idea of this agentic system would be to 00:11:04.279 --> 00:11:05.790 align:start position:0% idea of this agentic system would be to integrate<00:11:04.680> those<00:11:04.839> metrics<00:11:05.240> so<00:11:05.519> that<00:11:05.680> the 00:11:05.790 --> 00:11:05.800 align:start position:0% integrate those metrics so that the 00:11:05.800 --> 00:11:08.150 align:start position:0% integrate those metrics so that the agent<00:11:06.160> can<00:11:06.360> proactively<00:11:07.320> take<00:11:07.560> the<00:11:07.720> necessary 00:11:08.150 --> 00:11:08.160 align:start position:0% agent can proactively take the necessary 00:11:08.160 --> 00:11:10.190 align:start position:0% agent can proactively take the necessary measures<00:11:08.760> for<00:11:08.920> example<00:11:09.200> manager<00:11:09.600> node<00:11:09.880> if<00:11:10.079> you 00:11:10.190 --> 00:11:10.200 align:start position:0% measures for example manager node if you 00:11:10.200 --> 00:11:11.949 align:start position:0% measures for example manager node if you see<00:11:10.360> that<00:11:10.480> your<00:11:10.560> peers<00:11:10.839> are<00:11:10.920> getting<00:11:11.120> too<00:11:11.320> low 00:11:11.949 --> 00:11:11.959 align:start position:0% see that your peers are getting too low 00:11:11.959 --> 00:11:14.710 align:start position:0% see that your peers are getting too low maybe<00:11:12.200> you<00:11:12.360> need<00:11:12.519> to<00:11:13.200> well<00:11:13.399> do<00:11:13.639> something 00:11:14.710 --> 00:11:14.720 align:start position:0% maybe you need to well do something 00:11:14.720 --> 00:11:19.430 align:start position:0% maybe you need to well do something to<00:11:15.720> um<00:11:16.079> to<00:11:16.279> fix<00:11:16.560> that<00:11:17.360> um<00:11:17.839> yeah<00:11:18.399> that<00:11:19.000> is<00:11:19.120> all<00:11:19.279> I 00:11:19.430 --> 00:11:19.440 align:start position:0% to um to fix that um yeah that is all I 00:11:19.440 --> 00:11:23.030 align:start position:0% to um to fix that um yeah that is all I have<00:11:19.560> for<00:11:19.720> you<00:11:20.160> so<00:11:20.360> then<00:11:20.519> I<00:11:20.680> only<00:11:21.160> have<00:11:21.760> a<00:11:22.760> thank 00:11:23.030 --> 00:11:23.040 align:start position:0% have for you so then I only have a thank 00:11:23.040 --> 00:11:27.110 align:start position:0% have for you so then I only have a thank you<00:11:23.399> slight<00:11:24.279> left<00:11:25.279> um<00:11:25.680> obviously<00:11:26.600> Mario<00:11:26.959> and 00:11:27.110 --> 00:11:27.120 align:start position:0% you slight left um obviously Mario and 00:11:27.120 --> 00:11:29.629 align:start position:0% you slight left um obviously Mario and Josh<00:11:27.720> it<00:11:27.839> was<00:11:28.040> amazing<00:11:28.639> thanks<00:11:28.839> so<00:11:28.959> much<00:11:29.320> for 00:11:29.629 --> 00:11:29.639 align:start position:0% Josh it was amazing thanks so much for 00:11:29.639 --> 00:11:31.310 align:start position:0% Josh it was amazing thanks so much for uh<00:11:29.920> well<00:11:30.120> all<00:11:30.279> the<00:11:30.480> time<00:11:30.639> and<00:11:30.760> effort<00:11:31.040> that<00:11:31.160> you 00:11:31.310 --> 00:11:31.320 align:start position:0% uh well all the time and effort that you 00:11:31.320 --> 00:11:32.750 align:start position:0% uh well all the time and effort that you guys<00:11:31.480> spent<00:11:31.760> and<00:11:32.120> granting<00:11:32.440> us<00:11:32.600> this 00:11:32.750 --> 00:11:32.760 align:start position:0% guys spent and granting us this 00:11:32.760 --> 00:11:35.269 align:start position:0% guys spent and granting us this opportunity<00:11:33.480> to<00:11:33.639> be<00:11:33.800> part<00:11:33.959> of<00:11:34.079> the 00:11:35.269 --> 00:11:35.279 align:start position:0% opportunity to be part of the 00:11:35.279 --> 00:11:37.829 align:start position:0% opportunity to be part of the EPF<00:11:36.279> um<00:11:36.760> yeah<00:11:36.959> I<00:11:37.079> think<00:11:37.279> that's<00:11:37.440> it<00:11:37.600> so<00:11:37.720> if 00:11:37.829 --> 00:11:37.839 align:start position:0% EPF um yeah I think that's it so if 00:11:37.839 --> 00:11:39.790 align:start position:0% EPF um yeah I think that's it so if there<00:11:37.920> are<00:11:38.000> any<00:11:38.200> questions 00:11:39.790 --> 00:11:39.800 align:start position:0% there are any questions 00:11:39.800 --> 00:11:47.069 align:start position:0% there are any questions [Applause] 00:11:47.069 --> 00:11:47.079 align:start position:0% 00:11:47.079 --> 00:11:49.710 align:start position:0% then 00:11:49.710 --> 00:11:49.720 align:start position:0% then 00:11:49.720 --> 00:11:52.230 align:start position:0% then yeah<00:11:50.720> uh<00:11:50.920> hey<00:11:51.120> thank<00:11:51.279> you<00:11:51.399> for<00:11:51.639> an<00:11:51.839> amazing 00:11:52.230 --> 00:11:52.240 align:start position:0% yeah uh hey thank you for an amazing 00:11:52.240 --> 00:11:55.269 align:start position:0% yeah uh hey thank you for an amazing talk<00:11:53.120> uh<00:11:53.480> I<00:11:53.639> was<00:11:54.000> wondering<00:11:54.480> if<00:11:54.639> the<00:11:54.880> notes 00:11:55.269 --> 00:11:55.279 align:start position:0% talk uh I was wondering if the notes 00:11:55.279 --> 00:11:58.269 align:start position:0% talk uh I was wondering if the notes that<00:11:55.480> you<00:11:55.760> ran<00:11:56.320> were<00:11:56.600> validators<00:11:57.360> or<00:11:57.680> just 00:11:58.269 --> 00:11:58.279 align:start position:0% that you ran were validators or just 00:11:58.279 --> 00:12:01.870 align:start position:0% that you ran were validators or just notes<00:11:59.240> no<00:11:59.399> also<00:11:59.639> validators<00:12:00.480> also<00:12:00.880> validators 00:12:01.870 --> 00:12:01.880 align:start position:0% notes no also validators also validators 00:12:01.880 --> 00:12:04.470 align:start position:0% notes no also validators also validators okay<00:12:02.040> so<00:12:02.279> it<00:12:02.519> might<00:12:02.800> be<00:12:03.399> uh<00:12:03.560> nice<00:12:03.839> to<00:12:04.000> see<00:12:04.279> the 00:12:04.470 --> 00:12:04.480 align:start position:0% okay so it might be uh nice to see the 00:12:04.480 --> 00:12:06.870 align:start position:0% okay so it might be uh nice to see the difference<00:12:04.880> between<00:12:05.720> like<00:12:05.959> a<00:12:06.440> for<00:12:06.639> each 00:12:06.870 --> 00:12:06.880 align:start position:0% difference between like a for each 00:12:06.880 --> 00:12:08.509 align:start position:0% difference between like a for each client<00:12:07.440> what's<00:12:07.720> different<00:12:08.040> if<00:12:08.160> they're<00:12:08.320> a 00:12:08.509 --> 00:12:08.519 align:start position:0% client what's different if they're a 00:12:08.519 --> 00:12:10.990 align:start position:0% client what's different if they're a validator<00:12:09.519> and<00:12:09.839> if<00:12:10.000> they're<00:12:10.200> not<00:12:10.760> yeah<00:12:10.880> I 00:12:10.990 --> 00:12:11.000 align:start position:0% validator and if they're not yeah I 00:12:11.000 --> 00:12:12.389 align:start position:0% validator and if they're not yeah I agree<00:12:11.279> there's<00:12:11.480> lots<00:12:11.680> of<00:12:11.839> experiments<00:12:12.279> you 00:12:12.389 --> 00:12:12.399 align:start position:0% agree there's lots of experiments you 00:12:12.399 --> 00:12:15.350 align:start position:0% agree there's lots of experiments you could<00:12:12.600> do<00:12:13.279> um<00:12:13.519> really<00:12:14.040> really<00:12:14.240> lots<00:12:14.519> more<00:12:15.040> uh<00:12:15.279> I 00:12:15.350 --> 00:12:15.360 align:start position:0% could do um really really lots more uh I 00:12:15.360 --> 00:12:16.470 align:start position:0% could do um really really lots more uh I would<00:12:15.480> have<00:12:15.600> liked<00:12:15.800> to<00:12:15.880> have<00:12:16.000> done<00:12:16.160> more<00:12:16.320> of 00:12:16.470 --> 00:12:16.480 align:start position:0% would have liked to have done more of 00:12:16.480 --> 00:12:18.829 align:start position:0% would have liked to have done more of them<00:12:17.079> but<00:12:17.240> it's<00:12:17.760> as<00:12:17.880> BMA<00:12:18.199> already<00:12:18.399> said<00:12:18.680> it's 00:12:18.829 --> 00:12:18.839 align:start position:0% them but it's as BMA already said it's 00:12:18.839 --> 00:12:20.310 align:start position:0% them but it's as BMA already said it's quite<00:12:19.040> overwhelming<00:12:19.600> because<00:12:19.839> even<00:12:20.040> when<00:12:20.160> I 00:12:20.310 --> 00:12:20.320 align:start position:0% quite overwhelming because even when I 00:12:20.320 --> 00:12:21.790 align:start position:0% quite overwhelming because even when I thought<00:12:20.480> I<00:12:20.639> had<00:12:20.760> all<00:12:20.880> the<00:12:21.000> pieces<00:12:21.399> and<00:12:21.519> sort<00:12:21.680> of 00:12:21.790 --> 00:12:21.800 align:start position:0% thought I had all the pieces and sort of 00:12:21.800 --> 00:12:23.470 align:start position:0% thought I had all the pieces and sort of working<00:12:22.560> and<00:12:22.680> then<00:12:22.800> you<00:12:22.920> need<00:12:23.079> to<00:12:23.240> learn 00:12:23.470 --> 00:12:23.480 align:start position:0% working and then you need to learn 00:12:23.480 --> 00:12:25.069 align:start position:0% working and then you need to learn promql<00:12:23.880> okay<00:12:24.320> and<00:12:24.440> then<00:12:24.519> you<00:12:24.600> learn<00:12:24.800> a<00:12:24.880> bit<00:12:25.000> of 00:12:25.069 --> 00:12:25.079 align:start position:0% promql okay and then you learn a bit of 00:12:25.079 --> 00:12:26.750 align:start position:0% promql okay and then you learn a bit of promql<00:12:25.440> and<00:12:25.639> then<00:12:25.720> you<00:12:25.839> see<00:12:26.120> all<00:12:26.240> the<00:12:26.399> metrics 00:12:26.750 --> 00:12:26.760 align:start position:0% promql and then you see all the metrics 00:12:26.760 --> 00:12:29.670 align:start position:0% promql and then you see all the metrics that<00:12:26.839> are<00:12:27.440> there<00:12:28.440> for<00:12:28.600> example<00:12:28.880> Gra<00:12:29.480> which<00:12:29.560> I 00:12:29.670 --> 00:12:29.680 align:start position:0% that are there for example Gra which I 00:12:29.680 --> 00:12:30.949 align:start position:0% that are there for example Gra which I also<00:12:29.839> used<00:12:30.040> a<00:12:30.160> little<00:12:30.279> bit<00:12:30.440> at<00:12:30.519> somebody<00:12:30.839> I 00:12:30.949 --> 00:12:30.959 align:start position:0% also used a little bit at somebody I 00:12:30.959 --> 00:12:33.829 align:start position:0% also used a little bit at somebody I just<00:12:31.079> decided<00:12:31.519> okay<00:12:32.000> just<00:12:32.160> cannot<00:12:32.399> do<00:12:32.560> it<00:12:33.320> so 00:12:33.829 --> 00:12:33.839 align:start position:0% just decided okay just cannot do it so 00:12:33.839 --> 00:12:36.030 align:start position:0% just decided okay just cannot do it so yeah<00:12:33.959> I<00:12:34.079> agree<00:12:34.360> there's<00:12:34.600> lots<00:12:34.839> more<00:12:35.440> um<00:12:35.800> and 00:12:36.030 --> 00:12:36.040 align:start position:0% yeah I agree there's lots more um and 00:12:36.040 --> 00:12:37.430 align:start position:0% yeah I agree there's lots more um and those<00:12:36.480> those<00:12:36.639> things<00:12:36.839> would<00:12:36.959> be<00:12:37.120> interesting 00:12:37.430 --> 00:12:37.440 align:start position:0% those those things would be interesting 00:12:37.440 --> 00:12:39.949 align:start position:0% those those things would be interesting to<00:12:37.560> look<00:12:37.720> at<00:12:37.959> you<00:12:38.600> amazing<00:12:39.040> thank 00:12:39.949 --> 00:12:39.959 align:start position:0% to look at you amazing thank 00:12:39.959 --> 00:12:42.750 align:start position:0% to look at you amazing thank you<00:12:40.959> any<00:12:41.160> other 00:12:42.750 --> 00:12:42.760 align:start position:0% you any other 00:12:42.760 --> 00:12:44.470 align:start position:0% you any other questions 00:12:44.470 --> 00:12:44.480 align:start position:0% questions 00:12:44.480 --> 00:12:47.269 align:start position:0% questions Mario<00:12:45.480> um<00:12:45.880> yeah<00:12:46.360> um<00:12:46.639> yeah<00:12:46.760> I<00:12:46.839> was<00:12:46.959> wondering 00:12:47.269 --> 00:12:47.279 align:start position:0% Mario um yeah um yeah I was wondering 00:12:47.279 --> 00:12:49.269 align:start position:0% Mario um yeah um yeah I was wondering because<00:12:47.480> you<00:12:47.639> mentioned<00:12:48.079> the<00:12:48.279> setup<00:12:48.560> with<00:12:48.720> brm 00:12:49.269 --> 00:12:49.279 align:start position:0% because you mentioned the setup with brm 00:12:49.279 --> 00:12:51.269 align:start position:0% because you mentioned the setup with brm and<00:12:49.440> then<00:12:49.560> you<00:12:49.639> want<00:12:49.800> to<00:12:50.120> automatize<00:12:50.680> it<00:12:51.000> setup 00:12:51.269 --> 00:12:51.279 align:start position:0% and then you want to automatize it setup 00:12:51.279 --> 00:12:53.670 align:start position:0% and then you want to automatize it setup with<00:12:51.440> NEX<00:12:51.959> it's<00:12:52.120> really<00:12:52.320> cool<00:12:52.880> uh<00:12:53.000> I'm<00:12:53.160> just 00:12:53.670 --> 00:12:53.680 align:start position:0% with NEX it's really cool uh I'm just 00:12:53.680 --> 00:12:55.189 align:start position:0% with NEX it's really cool uh I'm just did<00:12:53.959> you<00:12:54.079> didn't<00:12:54.320> really<00:12:54.480> have<00:12:54.639> in<00:12:54.839> slides 00:12:55.189 --> 00:12:55.199 align:start position:0% did you didn't really have in slides 00:12:55.199 --> 00:12:56.790 align:start position:0% did you didn't really have in slides like<00:12:55.320> some<00:12:55.480> more<00:12:55.680> specs<00:12:56.000> about<00:12:56.240> it<00:12:56.480> like<00:12:56.639> for 00:12:56.790 --> 00:12:56.800 align:start position:0% like some more specs about it like for 00:12:56.800 --> 00:12:58.790 align:start position:0% like some more specs about it like for example<00:12:57.560> uh<00:12:57.680> what<00:12:57.800> are<00:12:58.079> what<00:12:58.199> virtualization 00:12:58.790 --> 00:12:58.800 align:start position:0% example uh what are what virtualization 00:12:58.800 --> 00:13:01.189 align:start position:0% example uh what are what virtualization are<00:12:58.920> you<00:12:59.199> using<00:12:59.399> with<00:12:59.519> Pro<00:12:59.760> Mars<00:13:00.160> like<00:13:00.480> uh<00:13:00.600> KVM 00:13:01.189 --> 00:13:01.199 align:start position:0% are you using with Pro Mars like uh KVM 00:13:01.199 --> 00:13:04.629 align:start position:0% are you using with Pro Mars like uh KVM or<00:13:01.440> lxc<00:13:02.199> or<00:13:02.639> yeah<00:13:02.959> KVM<00:13:03.440> is<00:13:03.519> what<00:13:03.639> I'm<00:13:03.760> using<00:13:04.199> but 00:13:04.629 --> 00:13:04.639 align:start position:0% or lxc or yeah KVM is what I'm using but 00:13:04.639 --> 00:13:06.389 align:start position:0% or lxc or yeah KVM is what I'm using but I<00:13:04.720> could<00:13:04.920> explore<00:13:05.360> maybe<00:13:05.680> Alternatives<00:13:06.279> I 00:13:06.389 --> 00:13:06.399 align:start position:0% I could explore maybe Alternatives I 00:13:06.399 --> 00:13:07.910 align:start position:0% I could explore maybe Alternatives I haven't<00:13:06.639> explored<00:13:07.000> any<00:13:07.199> alternatives<00:13:07.720> there 00:13:07.910 --> 00:13:07.920 align:start position:0% haven't explored any alternatives there 00:13:07.920 --> 00:13:10.550 align:start position:0% haven't explored any alternatives there so<00:13:08.839> you<00:13:08.959> think<00:13:09.120> it's<00:13:09.320> worth<00:13:09.560> exploring<00:13:10.399> uh 00:13:10.550 --> 00:13:10.560 align:start position:0% so you think it's worth exploring uh 00:13:10.560 --> 00:13:12.069 align:start position:0% so you think it's worth exploring uh just<00:13:10.720> the<00:13:10.800> Linux<00:13:11.160> containers<00:13:11.560> are<00:13:11.800> good<00:13:11.920> for 00:13:12.069 --> 00:13:12.079 align:start position:0% just the Linux containers are good for 00:13:12.079 --> 00:13:13.910 align:start position:0% just the Linux containers are good for servers<00:13:12.519> as<00:13:12.639> well<00:13:13.079> uh<00:13:13.240> and<00:13:13.320> I<00:13:13.399> was<00:13:13.560> wondering 00:13:13.910 --> 00:13:13.920 align:start position:0% servers as well uh and I was wondering 00:13:13.920 --> 00:13:15.829 align:start position:0% servers as well uh and I was wondering like<00:13:14.040> because<00:13:14.240> proxo<00:13:14.760> supports<00:13:15.160> both<00:13:15.519> and<00:13:15.639> you 00:13:15.829 --> 00:13:15.839 align:start position:0% like because proxo supports both and you 00:13:15.839 --> 00:13:17.629 align:start position:0% like because proxo supports both and you just<00:13:16.480> yeah<00:13:16.639> you<00:13:16.760> didn't<00:13:16.959> have<00:13:17.120> the<00:13:17.320> details 00:13:17.629 --> 00:13:17.639 align:start position:0% just yeah you didn't have the details 00:13:17.639 --> 00:13:18.870 align:start position:0% just yeah you didn't have the details there<00:13:17.760> so<00:13:17.920> I<00:13:17.959> was<00:13:18.079> wondering<00:13:18.399> like<00:13:18.560> which<00:13:18.639> one 00:13:18.870 --> 00:13:18.880 align:start position:0% there so I was wondering like which one 00:13:18.880 --> 00:13:20.629 align:start position:0% there so I was wondering like which one no<00:13:19.000> this<00:13:19.120> is<00:13:19.199> true<00:13:19.440> no<00:13:19.680> this<00:13:19.959> uh<00:13:20.120> I<00:13:20.240> use<00:13:20.480> it's 00:13:20.629 --> 00:13:20.639 align:start position:0% no this is true no this uh I use it's 00:13:20.639 --> 00:13:22.030 align:start position:0% no this is true no this uh I use it's the<00:13:20.800> lightweight<00:13:21.240> version<00:13:21.600> right<00:13:21.720> so<00:13:21.880> for 00:13:22.030 --> 00:13:22.040 align:start position:0% the lightweight version right so for 00:13:22.040 --> 00:13:24.269 align:start position:0% the lightweight version right so for Linux<00:13:22.320> that's<00:13:22.560> a<00:13:22.920> that's<00:13:23.040> a<00:13:23.600> preferred<00:13:24.000> option 00:13:24.269 --> 00:13:24.279 align:start position:0% Linux that's a that's a preferred option 00:13:24.279 --> 00:13:26.990 align:start position:0% Linux that's a that's a preferred option I<00:13:24.360> would<00:13:24.519> say<00:13:25.199> cool<00:13:25.519> thank<00:13:25.639> you<00:13:25.720> so<00:13:25.800> much 00:13:26.990 --> 00:13:27.000 align:start position:0% I would say cool thank you so much 00:13:27.000 --> 00:13:30.540 align:start position:0% I would say cool thank you so much here<00:13:28.000> all<00:13:28.120> right<00:13:28.399> thank<00:13:28.560> you<00:13:28.800> guys 00:13:30.540 --> 00:13:30.550 align:start position:0% here all right thank you guys 00:13:30.550 --> 00:13:34.650 align:start position:0% here all right thank you guys [Applause]