WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:14.799 align:start position:0% [Applause] 00:00:14.799 --> 00:00:14.809 align:start position:0% 00:00:14.809 --> 00:00:20.120 align:start position:0% has<00:00:15.809> to<00:00:16.020> skilful<00:00:17.330> place<00:00:18.330> to<00:00:18.599> have<00:00:18.990> some<00:00:19.980> of 00:00:20.120 --> 00:00:20.130 align:start position:0% has to skilful place to have some of 00:00:20.130 --> 00:00:26.439 align:start position:0% has to skilful place to have some of these<00:00:20.279> five<00:00:21.920> so<00:00:22.920> the<00:00:23.820> official<00:00:24.440> title 00:00:26.439 --> 00:00:26.449 align:start position:0% these five so the official title 00:00:26.449 --> 00:00:40.160 align:start position:0% these five so the official title techniques<00:00:31.070> this<00:00:32.070> is<00:00:32.129> the<00:00:38.690> better<00:00:39.690> one<00:00:39.989> will 00:00:40.160 --> 00:00:40.170 align:start position:0% techniques this is the better one will 00:00:40.170 --> 00:00:52.990 align:start position:0% techniques this is the better one will be<00:00:40.320> how<00:00:41.040> to<00:00:41.100> be<00:00:41.399> able<00:00:41.460> to<00:00:41.640> fight<00:00:42.000> again<00:00:46.760> yeah 00:00:52.990 --> 00:00:53.000 align:start position:0% 00:00:53.000 --> 00:01:03.799 align:start position:0% okay<00:00:56.629> but<00:00:57.629> thirty<00:00:57.930> two<00:00:58.050> sides<00:01:01.789> say<00:01:02.789> this<00:01:03.660> is 00:01:03.799 --> 00:01:03.809 align:start position:0% okay but thirty two sides say this is 00:01:03.809 --> 00:01:14.600 align:start position:0% okay but thirty two sides say this is not<00:01:04.020> talk<00:01:04.649> about<00:01:12.409> all<00:01:13.409> thing<00:01:13.740> I<00:01:13.920> am<00:01:14.220> going<00:01:14.460> to 00:01:14.600 --> 00:01:14.610 align:start position:0% not talk about all thing I am going to 00:01:14.610 --> 00:01:19.780 align:start position:0% not talk about all thing I am going to talk<00:01:14.790> about 00:01:19.780 --> 00:01:19.790 align:start position:0% 00:01:19.790 --> 00:01:23.340 align:start position:0% [Music] 00:01:23.340 --> 00:01:23.350 align:start position:0% [Music] 00:01:23.350 --> 00:01:26.520 align:start position:0% [Music] for<00:01:23.640> nothing<00:01:24.640> because<00:01:25.210> of<00:01:25.510> that<00:01:26.050> produces 00:01:26.520 --> 00:01:26.530 align:start position:0% for nothing because of that produces 00:01:26.530 --> 00:01:30.890 align:start position:0% for nothing because of that produces advanced<00:01:27.010> degrees<00:01:27.430> in<00:01:28.650> the<00:01:29.650> generic 00:01:30.890 --> 00:01:30.900 align:start position:0% advanced degrees in the generic 00:01:30.900 --> 00:01:35.070 align:start position:0% advanced degrees in the generic interpersonal<00:01:31.900> simulation<00:01:32.530> space<00:01:33.870> my<00:01:34.870> name 00:01:35.070 --> 00:01:35.080 align:start position:0% interpersonal simulation space my name 00:01:35.080 --> 00:01:39.149 align:start position:0% interpersonal simulation space my name is<00:01:35.229> Paulo<00:01:35.860> good<00:01:36.160> job<00:01:36.520> and<00:01:36.820> I<00:01:37.290> was<00:01:38.290> for<00:01:38.979> many 00:01:39.149 --> 00:01:39.159 align:start position:0% is Paulo good job and I was for many 00:01:39.159 --> 00:01:44.030 align:start position:0% is Paulo good job and I was for many years<00:01:39.250> I<00:01:39.580> do<00:01:39.640> enhance<00:01:41.100> so<00:01:42.100> let<00:01:42.430> me<00:01:42.610> go<00:01:42.790> through 00:01:44.030 --> 00:01:44.040 align:start position:0% years I do enhance so let me go through 00:01:44.040 --> 00:01:47.810 align:start position:0% years I do enhance so let me go through like<00:01:45.040> my<00:01:45.310> history<00:01:45.790> of<00:01:45.880> working<00:01:46.810> with<00:01:46.869> EPM<00:01:47.350> I 00:01:47.810 --> 00:01:47.820 align:start position:0% like my history of working with EPM I 00:01:47.820 --> 00:01:51.120 align:start position:0% like my history of working with EPM I started<00:01:48.820> quite<00:01:49.450> an<00:01:49.600> elite<00:01:49.810> even<00:01:50.560> before<00:01:50.740> the 00:01:51.120 --> 00:01:51.130 align:start position:0% started quite an elite even before the 00:01:51.130 --> 00:01:54.870 align:start position:0% started quite an elite even before the team<00:01:51.520> has<00:01:51.759> life<00:01:51.970> and<00:01:53.160> the<00:01:54.160> first<00:01:54.400> project<00:01:54.640> I 00:01:54.870 --> 00:01:54.880 align:start position:0% team has life and the first project I 00:01:54.880 --> 00:01:58.109 align:start position:0% team has life and the first project I was<00:01:55.000> working<00:01:55.390> for<00:01:55.720> with<00:01:56.080> my<00:01:56.350> colleague<00:01:57.119> was 00:01:58.109 --> 00:01:58.119 align:start position:0% was working for with my colleague was 00:01:58.119 --> 00:02:01.620 align:start position:0% was working for with my colleague was EDM<00:01:58.660> jet<00:01:58.930> so<00:01:59.259> it<00:01:59.500> was<00:01:59.710> it<00:02:00.700> was<00:02:00.880> a<00:02:00.910> product<00:02:01.300> that 00:02:01.620 --> 00:02:01.630 align:start position:0% EDM jet so it was it was a product that 00:02:01.630 --> 00:02:08.100 align:start position:0% EDM jet so it was it was a product that was<00:02:01.810> supposed<00:02:02.649> to<00:02:02.830> prove<00:02:03.039> that<00:02:03.340> in<00:02:03.820> the<00:02:04.000> end<00:02:07.110> it 00:02:08.100 --> 00:02:08.110 align:start position:0% was supposed to prove that in the end it 00:02:08.110 --> 00:02:12.030 align:start position:0% was supposed to prove that in the end it was<00:02:08.320> working<00:02:08.739> by<00:02:08.979> was<00:02:09.989> translating<00:02:10.989> he<00:02:11.620> my 00:02:12.030 --> 00:02:12.040 align:start position:0% was working by was translating he my 00:02:12.040 --> 00:02:14.930 align:start position:0% was working by was translating he my coach<00:02:12.340> to<00:02:12.640> be<00:02:13.270> my<00:02:13.450> heart<00:02:13.780> and<00:02:14.050> their<00:02:14.560> music 00:02:14.930 --> 00:02:14.940 align:start position:0% coach to be my heart and their music 00:02:14.940 --> 00:02:19.830 align:start position:0% coach to be my heart and their music LLVM<00:02:15.940> doing<00:02:16.600> it<00:02:17.380> was<00:02:18.060> it<00:02:19.060> was<00:02:19.239> compiling<00:02:19.690> that 00:02:19.830 --> 00:02:19.840 align:start position:0% LLVM doing it was it was compiling that 00:02:19.840 --> 00:02:23.790 align:start position:0% LLVM doing it was it was compiling that to<00:02:20.350> machine<00:02:21.130> code<00:02:21.390> loaded<00:02:22.390> loaded<00:02:23.140> to<00:02:23.440> memory 00:02:23.790 --> 00:02:23.800 align:start position:0% to machine code loaded loaded to memory 00:02:23.800 --> 00:02:26.100 align:start position:0% to machine code loaded loaded to memory and<00:02:24.100> then<00:02:24.459> it<00:02:24.700> was<00:02:24.880> executed<00:02:25.510> as<00:02:25.660> a<00:02:25.690> native 00:02:26.100 --> 00:02:26.110 align:start position:0% and then it was executed as a native 00:02:26.110 --> 00:02:33.199 align:start position:0% and then it was executed as a native code<00:02:28.230> so<00:02:29.230> the<00:02:29.560> product<00:02:29.950> died<00:02:30.160> around<00:02:31.650> 2017 00:02:33.199 --> 00:02:33.209 align:start position:0% code so the product died around 2017 00:02:33.209 --> 00:02:36.090 align:start position:0% code so the product died around 2017 signals<00:02:34.209> mostly<00:02:34.600> not<00:02:34.750> interested 00:02:36.090 --> 00:02:36.100 align:start position:0% signals mostly not interested 00:02:36.100 --> 00:02:39.840 align:start position:0% signals mostly not interested like<00:02:36.820> using<00:02:37.030> it<00:02:37.750> Fedora<00:02:38.530> to<00:02:38.680> prove<00:02:38.920> it<00:02:39.040> long 00:02:39.840 --> 00:02:39.850 align:start position:0% like using it Fedora to prove it long 00:02:39.850 --> 00:02:42.420 align:start position:0% like using it Fedora to prove it long time<00:02:40.120> ago<00:02:40.390> it's<00:02:40.680> absolute<00:02:41.680> ago<00:02:41.920> but<00:02:42.220> I<00:02:42.250> think 00:02:42.420 --> 00:02:42.430 align:start position:0% time ago it's absolute ago but I think 00:02:42.430 --> 00:02:46.580 align:start position:0% time ago it's absolute ago but I think the<00:02:43.330> big<00:02:43.720> controversy<00:02:44.200> about<00:02:44.740> collages 00:02:46.580 --> 00:02:46.590 align:start position:0% the big controversy about collages 00:02:46.590 --> 00:02:49.920 align:start position:0% the big controversy about collages compilation<00:02:47.590> part<00:02:47.770> line<00:02:48.040> like<00:02:49.000> consensus 00:02:49.920 --> 00:02:49.930 align:start position:0% compilation part line like consensus 00:02:49.930 --> 00:02:57.390 align:start position:0% compilation part line like consensus critical<00:02:50.940> critical<00:02:55.530> but<00:02:56.530> what<00:02:56.860> actually<00:02:57.040> come 00:02:57.390 --> 00:02:57.400 align:start position:0% critical critical but what actually come 00:02:57.400 --> 00:02:59.970 align:start position:0% critical critical but what actually come out<00:02:57.550> out<00:02:58.000> of<00:02:58.270> the<00:02:58.630> end<00:02:59.080> of<00:02:59.230> the<00:02:59.290> product<00:02:59.650> was<00:02:59.800> a 00:02:59.970 --> 00:02:59.980 align:start position:0% out out of the end of the product was a 00:02:59.980 --> 00:03:03.090 align:start position:0% out out of the end of the product was a DMZ<00:03:00.250> which<00:03:00.760> was<00:03:01.060> attempt<00:03:01.810> to<00:03:02.020> and<00:03:02.320> still<00:03:02.920> is 00:03:03.090 --> 00:03:03.100 align:start position:0% DMZ which was attempt to and still is 00:03:03.100 --> 00:03:08.790 align:start position:0% DMZ which was attempt to and still is attempt<00:03:03.850> to<00:03:04.470> define<00:03:05.470> the<00:03:06.600> low-level<00:03:07.650> API<00:03:08.650> for 00:03:08.790 --> 00:03:08.800 align:start position:0% attempt to define the low-level API for 00:03:08.800 --> 00:03:12.360 align:start position:0% attempt to define the low-level API for a<00:03:09.070> VM<00:03:09.460> and<00:03:09.900> actually<00:03:10.900> for<00:03:11.110> both<00:03:11.260> sides<00:03:11.590> or<00:03:11.920> ETS 00:03:12.360 --> 00:03:12.370 align:start position:0% a VM and actually for both sides or ETS 00:03:12.370 --> 00:03:15.840 align:start position:0% a VM and actually for both sides or ETS and<00:03:12.730> acquire<00:03:13.090> those<00:03:13.390> days<00:03:13.840> and<00:03:14.380> is<00:03:15.250> one<00:03:15.580> of<00:03:15.730> the 00:03:15.840 --> 00:03:15.850 align:start position:0% and acquire those days and is one of the 00:03:15.850 --> 00:03:19.260 align:start position:0% and acquire those days and is one of the site<00:03:16.060> implemented<00:03:16.870> it<00:03:17.440> can<00:03:17.680> use<00:03:18.270> like 00:03:19.260 --> 00:03:19.270 align:start position:0% site implemented it can use like 00:03:19.270 --> 00:03:23.160 align:start position:0% site implemented it can use like different<00:03:19.780> implementations<00:03:20.650> of<00:03:20.920> EBS<00:03:22.170> more 00:03:23.160 --> 00:03:23.170 align:start position:0% different implementations of EBS more 00:03:23.170 --> 00:03:30.350 align:start position:0% different implementations of EBS more more<00:03:23.680> like<00:03:23.860> a<00:03:24.660> way<00:03:25.660> of<00:03:25.870> as<00:03:26.260> a<00:03:26.590> supply<00:03:27.100> base<00:03:27.130> work 00:03:30.350 --> 00:03:30.360 align:start position:0% 00:03:30.360 --> 00:03:35.970 align:start position:0% and<00:03:31.680> the<00:03:32.680> first<00:03:32.980> point<00:03:33.730> here<00:03:34.000> is<00:03:34.350> a<00:03:35.350> project 00:03:35.970 --> 00:03:35.980 align:start position:0% and the first point here is a project 00:03:35.980 --> 00:03:38.460 align:start position:0% and the first point here is a project which<00:03:36.190> originally<00:03:36.940> was<00:03:37.090> the<00:03:37.480> CPP<00:03:37.990> is<00:03:38.080> helium 00:03:38.460 --> 00:03:38.470 align:start position:0% which originally was the CPP is helium 00:03:38.470 --> 00:03:42.720 align:start position:0% which originally was the CPP is helium and<00:03:38.710> it<00:03:39.340> has<00:03:39.820> my<00:03:40.030> big<00:03:40.300> C++<00:03:41.260> code<00:03:41.560> base<00:03:41.800> it<00:03:42.520> was 00:03:42.720 --> 00:03:42.730 align:start position:0% and it has my big C++ code base it was 00:03:42.730 --> 00:03:44.340 align:start position:0% and it has my big C++ code base it was one<00:03:42.940> of<00:03:42.970> the<00:03:43.180> free<00:03:43.360> implementation<00:03:43.570> was 00:03:44.340 --> 00:03:44.350 align:start position:0% one of the free implementation was 00:03:44.350 --> 00:03:47.400 align:start position:0% one of the free implementation was started<00:03:44.770> before<00:03:45.060> as<00:03:46.060> was<00:03:46.270> the<00:03:46.420> original<00:03:46.780> two 00:03:47.400 --> 00:03:47.410 align:start position:0% started before as was the original two 00:03:47.410 --> 00:03:52.200 align:start position:0% started before as was the original two implementations<00:03:49.530> but<00:03:50.530> there<00:03:51.280> actually<00:03:51.580> we 00:03:52.200 --> 00:03:52.210 align:start position:0% implementations but there actually we 00:03:52.210 --> 00:03:56.060 align:start position:0% implementations but there actually we also<00:03:52.390> use<00:03:52.780> the<00:03:53.110> e<00:03:53.140> BMC<00:03:53.650> API<00:03:53.950> in<00:03:54.310> fact<00:03:54.820> the<00:03:55.240> EVF 00:03:56.060 --> 00:03:56.070 align:start position:0% also use the e BMC API in fact the EVF 00:03:56.070 --> 00:03:58.170 align:start position:0% also use the e BMC API in fact the EVF implementations<00:03:57.070> from<00:03:57.220> the<00:03:57.460> window<00:03:57.820> into 00:03:58.170 --> 00:03:58.180 align:start position:0% implementations from the window into 00:03:58.180 --> 00:04:02.839 align:start position:0% implementations from the window into this<00:03:58.300> API<00:03:59.170> so<00:03:59.980> it's<00:04:00.160> it's<00:04:00.550> available<00:04:00.820> as 00:04:02.839 --> 00:04:02.849 align:start position:0% this API so it's it's available as 00:04:02.849 --> 00:04:05.729 align:start position:0% this API so it's it's available as and<00:04:03.849> the<00:04:03.969> last<00:04:04.090> product<00:04:04.420> is<00:04:04.629> he<00:04:04.780> in<00:04:04.959> wattage<00:04:05.439> I 00:04:05.729 --> 00:04:05.739 align:start position:0% and the last product is he in wattage I 00:04:05.739 --> 00:04:09.750 align:start position:0% and the last product is he in wattage I started<00:04:06.340> last<00:04:07.000> year<00:04:07.239> and<00:04:08.370> many<00:04:09.370> of<00:04:09.609> the<00:04:09.730> things 00:04:09.750 --> 00:04:09.760 align:start position:0% started last year and many of the things 00:04:09.760 --> 00:04:11.640 align:start position:0% started last year and many of the things most<00:04:10.269> of<00:04:10.510> the<00:04:10.599> things<00:04:10.810> I<00:04:10.989> am<00:04:11.109> I<00:04:11.230> going<00:04:11.409> to 00:04:11.640 --> 00:04:11.650 align:start position:0% most of the things I am I going to 00:04:11.650 --> 00:04:13.440 align:start position:0% most of the things I am I going to prevention<00:04:12.340> are<00:04:12.579> coming<00:04:12.909> from<00:04:13.060> from 00:04:13.440 --> 00:04:13.450 align:start position:0% prevention are coming from from 00:04:13.450 --> 00:04:16.909 align:start position:0% prevention are coming from from discoveries<00:04:14.109> to<00:04:14.379> this<00:04:14.500> product 00:04:16.909 --> 00:04:16.919 align:start position:0% 00:04:16.919 --> 00:04:21.539 align:start position:0% CPM<00:04:17.919> one<00:04:18.130> is<00:04:19.049> this<00:04:20.049> is<00:04:20.549> interpreter 00:04:21.539 --> 00:04:21.549 align:start position:0% CPM one is this is interpreter 00:04:21.549 --> 00:04:28.129 align:start position:0% CPM one is this is interpreter implementing<00:04:22.350> EVM<00:04:23.910> and<00:04:25.590> the<00:04:26.590> key<00:04:27.370> differences 00:04:28.129 --> 00:04:28.139 align:start position:0% implementing EVM and the key differences 00:04:28.139 --> 00:04:33.629 align:start position:0% implementing EVM and the key differences it<00:04:29.139> has<00:04:29.410> pretty<00:04:29.680> pretty<00:04:30.100> good<00:04:32.430> 256<00:04:33.430> bit 00:04:33.629 --> 00:04:33.639 align:start position:0% it has pretty pretty good 256 bit 00:04:33.639 --> 00:04:37.159 align:start position:0% it has pretty pretty good 256 bit integer<00:04:34.240> implementation<00:04:34.960> and<00:04:35.550> it<00:04:36.550> has<00:04:36.789> also 00:04:37.159 --> 00:04:37.169 align:start position:0% integer implementation and it has also 00:04:37.169 --> 00:04:41.129 align:start position:0% integer implementation and it has also experimental<00:04:39.150> efficient<00:04:40.150> different<00:04:40.840> way<00:04:40.960> of 00:04:41.129 --> 00:04:41.139 align:start position:0% experimental efficient different way of 00:04:41.139 --> 00:04:45.409 align:start position:0% experimental efficient different way of counting<00:04:41.919> castings<00:04:42.509> and<00:04:43.509> constraints<00:04:44.380> and 00:04:45.409 --> 00:04:45.419 align:start position:0% counting castings and constraints and 00:04:45.419 --> 00:04:50.189 align:start position:0% counting castings and constraints and firstly<00:04:46.419> my<00:04:47.050> other<00:04:48.660> optimizations<00:04:49.660> kind<00:04:50.080> of 00:04:50.189 --> 00:04:50.199 align:start position:0% firstly my other optimizations kind of 00:04:50.199 --> 00:04:52.680 align:start position:0% firstly my other optimizations kind of like<00:04:50.349> micro<00:04:51.099> micro<00:04:51.550> optimizations<00:04:51.639> which<00:04:52.509> are 00:04:52.680 --> 00:04:52.690 align:start position:0% like micro micro optimizations which are 00:04:52.690 --> 00:04:56.390 align:start position:0% like micro micro optimizations which are related<00:04:52.870> either<00:04:53.289> to<00:04:53.440> C++<00:04:53.770> or<00:04:54.430> maybe<00:04:55.240> not<00:04:55.479> but 00:04:56.390 --> 00:04:56.400 align:start position:0% related either to C++ or maybe not but 00:04:56.400 --> 00:05:00.300 align:start position:0% related either to C++ or maybe not but I'm<00:04:57.400> going<00:04:57.789> to<00:04:57.849> talk<00:04:58.090> about<00:04:58.150> the<00:04:58.570> first<00:04:59.310> 2.0 00:05:00.300 --> 00:05:00.310 align:start position:0% I'm going to talk about the first 2.0 00:05:00.310 --> 00:05:03.150 align:start position:0% I'm going to talk about the first 2.0 and<00:05:00.639> these<00:05:01.630> both<00:05:02.080> of<00:05:02.229> these<00:05:02.259> were<00:05:02.919> actually 00:05:03.150 --> 00:05:03.160 align:start position:0% and these both of these were actually 00:05:03.160 --> 00:05:08.779 align:start position:0% and these both of these were actually least<00:05:03.639> in<00:05:03.880> version<00:05:04.300> 0.1<00:05:06.180> sometime<00:05:07.180> ago<00:05:07.590> so 00:05:08.779 --> 00:05:08.789 align:start position:0% least in version 0.1 sometime ago so 00:05:08.789 --> 00:05:15.510 align:start position:0% least in version 0.1 sometime ago so they<00:05:09.789> were<00:05:09.970> down<00:05:10.210> at<00:05:10.599> the<00:05:10.960> same<00:05:11.169> time<00:05:13.199> so<00:05:14.520> when 00:05:15.510 --> 00:05:15.520 align:start position:0% they were down at the same time so when 00:05:15.520 --> 00:05:26.059 align:start position:0% they were down at the same time so when we<00:05:15.639> started<00:05:16.120> there 00:05:26.059 --> 00:05:26.069 align:start position:0% 00:05:26.069 --> 00:05:31.529 align:start position:0% when<00:05:27.069> we<00:05:27.190> want<00:05:27.430> to<00:05:27.550> start<00:05:27.819> with<00:05:28.740> the<00:05:29.819> two<00:05:30.819> 5/16 00:05:31.529 --> 00:05:31.539 align:start position:0% when we want to start with the two 5/16 00:05:31.539 --> 00:05:35.400 align:start position:0% when we want to start with the two 5/16 eater<00:05:31.860> implementation<00:05:33.539> so<00:05:34.539> we<00:05:34.840> can<00:05:35.020> say<00:05:35.229> it's 00:05:35.400 --> 00:05:35.410 align:start position:0% eater implementation so we can say it's 00:05:35.410 --> 00:05:38.189 align:start position:0% eater implementation so we can say it's critical<00:05:36.099> from<00:05:36.340> the<00:05:37.210> end<00:05:37.479> point<00:05:37.720> of<00:05:37.840> view<00:05:38.050> this 00:05:38.189 --> 00:05:38.199 align:start position:0% critical from the end point of view this 00:05:38.199 --> 00:05:43.589 align:start position:0% critical from the end point of view this but<00:05:38.470> this<00:05:38.919> is<00:05:39.220> the<00:05:39.699> arc<00:05:40.360> Maddox<00:05:40.780> ATM<00:05:41.650> uses<00:05:42.569> so<00:05:43.569> I 00:05:43.589 --> 00:05:43.599 align:start position:0% but this is the arc Maddox ATM uses so I 00:05:43.599 --> 00:05:47.159 align:start position:0% but this is the arc Maddox ATM uses so I chose<00:05:43.930> the<00:05:44.289> kind<00:05:44.530> of<00:05:44.620> like<00:05:44.770> most<00:05:45.550> realistic<00:05:46.169> is 00:05:47.159 --> 00:05:47.169 align:start position:0% chose the kind of like most realistic is 00:05:47.169 --> 00:05:50.520 align:start position:0% chose the kind of like most realistic is like<00:05:47.620> if<00:05:48.220> it's<00:05:48.460> maybe<00:05:49.330> it's<00:05:49.840> important<00:05:50.349> what 00:05:50.520 --> 00:05:50.530 align:start position:0% like if it's maybe it's important what 00:05:50.530 --> 00:05:53.219 align:start position:0% like if it's maybe it's important what might<00:05:50.710> be<00:05:50.830> so<00:05:51.580> much<00:05:51.789> but<00:05:52.150> was<00:05:52.330> my<00:05:52.509> expectation 00:05:53.219 --> 00:05:53.229 align:start position:0% might be so much but was my expectation 00:05:53.229 --> 00:06:09.790 align:start position:0% might be so much but was my expectation is<00:05:53.259> about<00:05:53.620> a<00:05:53.650> pound 00:06:09.790 --> 00:06:09.800 align:start position:0% 00:06:09.800 --> 00:06:14.200 align:start position:0% when<00:06:10.800> consumers<00:06:11.490> actually<00:06:12.590> recently<00:06:13.590> had 00:06:14.200 --> 00:06:14.210 align:start position:0% when consumers actually recently had 00:06:14.210 --> 00:06:17.450 align:start position:0% when consumers actually recently had option<00:06:15.210> to<00:06:15.419> actually<00:06:16.259> place<00:06:16.499> the<00:06:17.009> general 00:06:17.450 --> 00:06:17.460 align:start position:0% option to actually place the general 00:06:17.460 --> 00:06:21.439 align:start position:0% option to actually place the general implementation<00:06:18.180> of<00:06:18.379> affinity<00:06:19.379> group<00:06:19.999> in<00:06:20.999> a 00:06:21.439 --> 00:06:21.449 align:start position:0% implementation of affinity group in a 00:06:21.449 --> 00:06:23.779 align:start position:0% implementation of affinity group in a live<00:06:21.839> interpreter<00:06:22.199> which<00:06:22.889> previously<00:06:23.370> was 00:06:23.779 --> 00:06:23.789 align:start position:0% live interpreter which previously was 00:06:23.789 --> 00:06:26.110 align:start position:0% live interpreter which previously was using<00:06:24.150> boost<00:06:24.479> multi-position 00:06:26.110 --> 00:06:26.120 align:start position:0% using boost multi-position 00:06:26.120 --> 00:06:29.540 align:start position:0% using boost multi-position so<00:06:27.120> what<00:06:27.360> is<00:06:27.569> commonly<00:06:28.499> known<00:06:28.589> as<00:06:28.979> Sigma's 00:06:29.540 --> 00:06:29.550 align:start position:0% so what is commonly known as Sigma's 00:06:29.550 --> 00:06:32.719 align:start position:0% so what is commonly known as Sigma's glass<00:06:29.819> library<00:06:30.389> some<00:06:30.809> kind<00:06:31.050> of<00:06:31.729> standard 00:06:32.719 --> 00:06:32.729 align:start position:0% glass library some kind of standard 00:06:32.729 --> 00:06:36.200 align:start position:0% glass library some kind of standard library<00:06:33.330> extension<00:06:34.669> commonly<00:06:35.669> using<00:06:36.089> too 00:06:36.200 --> 00:06:36.210 align:start position:0% library extension commonly using too 00:06:36.210 --> 00:06:41.450 align:start position:0% library extension commonly using too many<00:06:36.330> C++<00:06:37.259> products<00:06:39.650> so<00:06:40.650> I<00:06:40.860> think<00:06:41.099> it's 00:06:41.450 --> 00:06:41.460 align:start position:0% many C++ products so I think it's 00:06:41.460 --> 00:06:43.070 align:start position:0% many C++ products so I think it's nothing<00:06:41.639> to<00:06:41.999> be<00:06:42.120> to<00:06:42.330> be<00:06:42.449> worried<00:06:42.629> about<00:06:42.779> it 00:06:43.070 --> 00:06:43.080 align:start position:0% nothing to be to be worried about it 00:06:43.080 --> 00:06:44.719 align:start position:0% nothing to be to be worried about it there's<00:06:43.319> it's<00:06:43.560> quite<00:06:43.919> year<00:06:44.219> better 00:06:44.719 --> 00:06:44.729 align:start position:0% there's it's quite year better 00:06:44.729 --> 00:06:49.249 align:start position:0% there's it's quite year better performance<00:06:46.460> but<00:06:47.659> with<00:06:48.659> an<00:06:48.779> option<00:06:49.139> to 00:06:49.249 --> 00:06:49.259 align:start position:0% performance but with an option to 00:06:49.259 --> 00:06:52.369 align:start position:0% performance but with an option to replace<00:06:49.589> that<00:06:50.400> implementation<00:06:51.060> with<00:06:51.449> index 00:06:52.369 --> 00:06:52.379 align:start position:0% replace that implementation with index 00:06:52.379 --> 00:06:54.739 align:start position:0% replace that implementation with index implementation<00:06:53.189> which<00:06:53.370> is<00:06:53.460> which<00:06:54.419> is<00:06:54.449> the 00:06:54.739 --> 00:06:54.749 align:start position:0% implementation which is which is the 00:06:54.749 --> 00:07:00.829 align:start position:0% implementation which is which is the implementation<00:06:55.259> actually<00:06:55.620> this<00:06:56.479> 440<00:06:57.479> bm1<00:06:59.839> at 00:07:00.829 --> 00:07:00.839 align:start position:0% implementation actually this 440 bm1 at 00:07:00.839 --> 00:07:03.260 align:start position:0% implementation actually this 440 bm1 at this<00:07:01.050> point<00:07:01.469> big<00:07:01.589> thanks<00:07:02.039> to<00:07:02.069> some<00:07:02.789> internet 00:07:03.260 --> 00:07:03.270 align:start position:0% this point big thanks to some internet 00:07:03.270 --> 00:07:04.730 align:start position:0% this point big thanks to some internet guy<00:07:03.539> called<00:07:03.870> Dastak<00:07:04.379> who<00:07:04.560> actually 00:07:04.730 --> 00:07:04.740 align:start position:0% guy called Dastak who actually 00:07:04.740 --> 00:07:08.899 align:start position:0% guy called Dastak who actually contributed<00:07:05.699> for<00:07:05.879> this<00:07:06.029> changes<00:07:06.889> and<00:07:07.909> use 00:07:08.899 --> 00:07:08.909 align:start position:0% contributed for this changes and use 00:07:08.909 --> 00:07:11.829 align:start position:0% contributed for this changes and use also<00:07:09.330> smaller<00:07:09.659> more<00:07:10.169> modest<00:07:10.529> like<00:07:10.710> that<00:07:10.919> so 00:07:11.829 --> 00:07:11.839 align:start position:0% also smaller more modest like that so 00:07:11.839 --> 00:07:17.170 align:start position:0% also smaller more modest like that so this<00:07:12.839> is<00:07:12.899> like<00:07:13.370> zoom<00:07:14.370> of<00:07:14.610> of<00:07:14.939> the<00:07:15.529> benchmark 00:07:17.170 --> 00:07:17.180 align:start position:0% this is like zoom of of the benchmark 00:07:17.180 --> 00:07:21.559 align:start position:0% this is like zoom of of the benchmark small<00:07:18.180> set<00:07:18.419> of<00:07:18.569> benchmarks<00:07:18.930> I<00:07:19.319> did<00:07:19.589> and<00:07:20.569> we 00:07:21.559 --> 00:07:21.569 align:start position:0% small set of benchmarks I did and we 00:07:21.569 --> 00:07:25.519 align:start position:0% small set of benchmarks I did and we will<00:07:22.050> going<00:07:22.469> back<00:07:22.830> to<00:07:23.009> that<00:07:23.189> again<00:07:23.839> but<00:07:24.839> simply 00:07:25.519 --> 00:07:25.529 align:start position:0% will going back to that again but simply 00:07:25.529 --> 00:07:30.070 align:start position:0% will going back to that again but simply by<00:07:25.649> replacing<00:07:26.629> the<00:07:27.629> teacher<00:07:28.050> implementation 00:07:30.070 --> 00:07:30.080 align:start position:0% by replacing the teacher implementation 00:07:30.080 --> 00:07:34.639 align:start position:0% by replacing the teacher implementation we<00:07:31.080> can<00:07:31.110> get<00:07:32.060> around<00:07:33.060> three<00:07:33.449> times<00:07:33.649> speed 00:07:34.639 --> 00:07:34.649 align:start position:0% we can get around three times speed 00:07:34.649 --> 00:07:41.290 align:start position:0% we can get around three times speed improvement 00:07:41.290 --> 00:07:41.300 align:start position:0% 00:07:41.300 --> 00:07:45.520 align:start position:0% this<00:07:41.690> is<00:07:41.840> summary<00:07:42.560> of<00:07:43.840> evolution<00:07:44.840> later<00:07:45.050> so 00:07:45.520 --> 00:07:45.530 align:start position:0% this is summary of evolution later so 00:07:45.530 --> 00:07:54.330 align:start position:0% this is summary of evolution later so it's<00:07:45.710> like<00:07:45.860> a<00:07:45.890> commercial<00:07:46.310> end<00:07:46.700> of<00:07:47.920> days<00:07:52.300> the 00:07:54.330 --> 00:07:54.340 align:start position:0% it's like a commercial end of days the 00:07:54.340 --> 00:08:03.700 align:start position:0% it's like a commercial end of days the average<00:07:55.420> usage<00:07:57.190> of<00:07:58.190> the<00:07:59.380> phones<00:08:00.380> here<00:08:01.780> but<00:08:02.780> if 00:08:03.700 --> 00:08:03.710 align:start position:0% average usage of the phones here but if 00:08:03.710 --> 00:08:08.920 align:start position:0% average usage of the phones here but if we<00:08:03.770> go<00:08:04.070> back<00:08:04.340> to<00:08:05.470> talking<00:08:06.470> about<00:08:07.450> this<00:08:08.450> to 00:08:08.920 --> 00:08:08.930 align:start position:0% we go back to talking about this to 00:08:08.930 --> 00:08:11.320 align:start position:0% we go back to talking about this to fight<00:08:09.370> experimentation<00:08:10.370> and<00:08:10.730> if<00:08:10.970> you<00:08:11.120> can 00:08:11.320 --> 00:08:11.330 align:start position:0% fight experimentation and if you can 00:08:11.330 --> 00:08:17.410 align:start position:0% fight experimentation and if you can refer<00:08:11.890> probably<00:08:12.890> very<00:08:13.370> overused<00:08:15.490> at2020<00:08:16.490> room 00:08:17.410 --> 00:08:17.420 align:start position:0% refer probably very overused at2020 room 00:08:17.420 --> 00:08:20.650 align:start position:0% refer probably very overused at2020 room so<00:08:18.110> for<00:08:18.410> if<00:08:18.740> you<00:08:18.920> want<00:08:19.100> to<00:08:19.250> implement<00:08:19.730> into 00:08:20.650 --> 00:08:20.660 align:start position:0% so for if you want to implement into 00:08:20.660 --> 00:08:24.850 align:start position:0% so for if you want to implement into drew<00:08:22.120> it's<00:08:23.120> actually<00:08:23.630> what's<00:08:23.840> most<00:08:24.110> mostly 00:08:24.850 --> 00:08:24.860 align:start position:0% drew it's actually what's most mostly 00:08:24.860 --> 00:08:29.800 align:start position:0% drew it's actually what's most mostly like<00:08:25.040> that<00:08:25.300> so<00:08:26.860> so<00:08:27.860> 80%<00:08:28.550> of<00:08:29.120> your<00:08:29.270> struggles 00:08:29.800 --> 00:08:29.810 align:start position:0% like that so so 80% of your struggles 00:08:29.810 --> 00:08:33.010 align:start position:0% like that so so 80% of your struggles around<00:08:30.350> division<00:08:30.980> which<00:08:31.460> is<00:08:31.750> pretty<00:08:32.750> magical 00:08:33.010 --> 00:08:33.020 align:start position:0% around division which is pretty magical 00:08:33.020 --> 00:08:36.460 align:start position:0% around division which is pretty magical place<00:08:33.580> to<00:08:34.580> do<00:08:34.729> anything<00:08:35.600> else<00:08:35.930> you<00:08:36.080> want<00:08:36.380> to 00:08:36.460 --> 00:08:36.470 align:start position:0% place to do anything else you want to 00:08:36.470 --> 00:08:39.070 align:start position:0% place to do anything else you want to implement<00:08:37.479> it's<00:08:38.479> pretty<00:08:38.840> much 00:08:39.070 --> 00:08:39.080 align:start position:0% implement it's pretty much 00:08:39.080 --> 00:08:40.170 align:start position:0% implement it's pretty much straightforward 00:08:40.170 --> 00:08:40.180 align:start position:0% straightforward 00:08:40.180 --> 00:08:43.510 align:start position:0% straightforward so<00:08:41.180> by<00:08:41.360> diffusion<00:08:41.660> here<00:08:41.990> I<00:08:42.050> was<00:08:42.229> so<00:08:42.410> mean 00:08:43.510 --> 00:08:43.520 align:start position:0% so by diffusion here I was so mean 00:08:43.520 --> 00:08:45.760 align:start position:0% so by diffusion here I was so mean reminded<00:08:44.480> of<00:08:44.570> the<00:08:44.660> division<00:08:45.110> of<00:08:45.200> my<00:08:45.440> module 00:08:45.760 --> 00:08:45.770 align:start position:0% reminded of the division of my module 00:08:45.770 --> 00:08:48.130 align:start position:0% reminded of the division of my module operations<00:08:46.610> and<00:08:47.000> so<00:08:47.150> on<00:08:47.330> because<00:08:47.540> like 00:08:48.130 --> 00:08:48.140 align:start position:0% operations and so on because like 00:08:48.140 --> 00:08:50.140 align:start position:0% operations and so on because like there's<00:08:48.440> lots<00:08:48.620> of<00:08:48.860> these<00:08:49.040> actually<00:08:49.820> coming 00:08:50.140 --> 00:08:50.150 align:start position:0% there's lots of these actually coming 00:08:50.150 --> 00:08:56.830 align:start position:0% there's lots of these actually coming from<00:08:50.180> from<00:08:50.660> the<00:08:50.780> same<00:08:50.990> algorithm<00:08:54.070> but<00:08:55.070> like<00:08:55.840> if 00:08:56.830 --> 00:08:56.840 align:start position:0% from from the same algorithm but like if 00:08:56.840 --> 00:09:00.040 align:start position:0% from from the same algorithm but like if we<00:08:57.080> like<00:08:57.670> consuming<00:08:58.670> like<00:08:58.910> a<00:08:58.940> short<00:08:59.360> short 00:09:00.040 --> 00:09:00.050 align:start position:0% we like consuming like a short short 00:09:00.050 --> 00:09:05.140 align:start position:0% we like consuming like a short short time<00:09:00.290> five<00:09:00.650> year<00:09:00.920> if<00:09:01.580> I<00:09:01.820> can<00:09:02.120> leave<00:09:02.980> quick<00:09:04.150> its 00:09:05.140 --> 00:09:05.150 align:start position:0% time five year if I can leave quick its 00:09:05.150 --> 00:09:10.210 align:start position:0% time five year if I can leave quick its how<00:09:05.510> how<00:09:05.930> like<00:09:07.240> how<00:09:08.240> to<00:09:08.300> I<00:09:08.870> think<00:09:09.740> the 00:09:10.210 --> 00:09:10.220 align:start position:0% how how like how to I think the 00:09:10.220 --> 00:09:15.259 align:start position:0% how how like how to I think the performing<00:09:11.440> two<00:09:12.440> five<00:09:12.650> six 00:09:15.259 --> 00:09:15.269 align:start position:0% 00:09:15.269 --> 00:09:17.689 align:start position:0% the<00:09:15.480> implementation<00:09:15.929> should<00:09:16.499> look<00:09:16.679> like<00:09:16.709> so 00:09:17.689 --> 00:09:17.699 align:start position:0% the implementation should look like so 00:09:17.699 --> 00:09:22.879 align:start position:0% the implementation should look like so these<00:09:18.240> are<00:09:19.369> some<00:09:20.369> guidelines<00:09:20.610> I<00:09:20.939> have<00:09:21.889> so 00:09:22.879 --> 00:09:22.889 align:start position:0% these are some guidelines I have so 00:09:22.889 --> 00:09:25.639 align:start position:0% these are some guidelines I have so first<00:09:23.160> of<00:09:23.369> all<00:09:23.490> you<00:09:24.149> can<00:09:24.360> forget<00:09:24.959> about<00:09:25.019> any 00:09:25.639 --> 00:09:25.649 align:start position:0% first of all you can forget about any 00:09:25.649 --> 00:09:28.340 align:start position:0% first of all you can forget about any any<00:09:26.040> kind<00:09:26.309> of<00:09:26.459> fancy<00:09:26.759> algorithm<00:09:27.749> that<00:09:27.929> show<00:09:28.170> up 00:09:28.340 --> 00:09:28.350 align:start position:0% any kind of fancy algorithm that show up 00:09:28.350 --> 00:09:36.100 align:start position:0% any kind of fancy algorithm that show up somewhere<00:09:28.709> in<00:09:29.160> the<00:09:30.949> space<00:09:32.329> and<00:09:33.329> one<00:09:33.540> most<00:09:33.809> like 00:09:36.100 --> 00:09:36.110 align:start position:0% 00:09:36.110 --> 00:09:40.340 align:start position:0% multiplication<00:09:37.110> algorithm<00:09:37.649> like<00:09:39.170> stage<00:09:40.170> to 00:09:40.340 --> 00:09:40.350 align:start position:0% multiplication algorithm like stage to 00:09:40.350 --> 00:09:52.369 align:start position:0% multiplication algorithm like stage to some<00:09:40.529> multiplications<00:09:41.459> of<00:09:41.819> the<00:09:42.119> words<00:09:51.139> so<00:09:52.139> I 00:09:52.369 --> 00:09:52.379 align:start position:0% some multiplications of the words so I 00:09:52.379 --> 00:09:55.460 align:start position:0% some multiplications of the words so I mean<00:09:52.619> they<00:09:52.949> work<00:09:53.389> as<00:09:54.389> export<00:09:55.110> where<00:09:55.379> they 00:09:55.460 --> 00:09:55.470 align:start position:0% mean they work as export where they 00:09:55.470 --> 00:09:59.720 align:start position:0% mean they work as export where they actually<00:09:56.420> beat<00:09:57.420> big<00:09:57.929> big<00:09:58.379> numbers<00:09:59.129> to<00:09:59.160> do 00:09:59.720 --> 00:09:59.730 align:start position:0% actually beat big big numbers to do 00:09:59.730 --> 00:10:02.859 align:start position:0% actually beat big big numbers to do multiplier<00:10:00.269> and<00:10:00.720> so<00:10:00.959> on<00:10:01.249> for<00:10:02.249> the<00:10:02.399> the 00:10:02.859 --> 00:10:02.869 align:start position:0% multiplier and so on for the the 00:10:02.869 --> 00:10:05.480 align:start position:0% multiplier and so on for the the procedure<00:10:03.869> is<00:10:04.139> actually<00:10:04.319> quite<00:10:04.740> quite<00:10:05.160> small 00:10:05.480 --> 00:10:05.490 align:start position:0% procedure is actually quite quite small 00:10:05.490 --> 00:10:09.109 align:start position:0% procedure is actually quite quite small precision<00:10:05.759> actually<00:10:06.709> comparing<00:10:07.709> two<00:10:08.119> numbers 00:10:09.109 --> 00:10:09.119 align:start position:0% precision actually comparing two numbers 00:10:09.119 --> 00:10:13.069 align:start position:0% precision actually comparing two numbers internal<00:10:10.110> so<00:10:11.149> none<00:10:12.149> of<00:10:12.179> them<00:10:12.420> are<00:10:12.540> needed<00:10:12.869> and 00:10:13.069 --> 00:10:13.079 align:start position:0% internal so none of them are needed and 00:10:13.079 --> 00:10:14.919 align:start position:0% internal so none of them are needed and I<00:10:13.319> am<00:10:13.589> pretty<00:10:13.829> sure<00:10:13.980> that's<00:10:14.279> that's<00:10:14.610> correct 00:10:14.919 --> 00:10:14.929 align:start position:0% I am pretty sure that's that's correct 00:10:14.929 --> 00:10:19.780 align:start position:0% I am pretty sure that's that's correct statement<00:10:17.179> but<00:10:18.179> what<00:10:18.480> I've<00:10:18.660> also<00:10:18.899> living<00:10:19.379> in 00:10:19.780 --> 00:10:19.790 align:start position:0% statement but what I've also living in 00:10:19.790 --> 00:10:23.119 align:start position:0% statement but what I've also living in Texas<00:10:20.790> I<00:10:21.360> actually<00:10:21.540> not<00:10:22.110> always<00:10:22.439> liked<00:10:22.799> easy 00:10:23.119 --> 00:10:23.129 align:start position:0% Texas I actually not always liked easy 00:10:23.129 --> 00:10:30.319 align:start position:0% Texas I actually not always liked easy cases<00:10:23.670> to<00:10:23.850> handle<00:10:28.069> so<00:10:29.069> even<00:10:29.910> if<00:10:30.029> you<00:10:30.149> have 00:10:30.319 --> 00:10:30.329 align:start position:0% cases to handle so even if you have 00:10:30.329 --> 00:10:33.889 align:start position:0% cases to handle so even if you have option<00:10:30.779> to<00:10:31.699> figure<00:10:32.699> out<00:10:32.819> that<00:10:33.119> the<00:10:33.509> numbers 00:10:33.889 --> 00:10:33.899 align:start position:0% option to figure out that the numbers 00:10:33.899 --> 00:10:36.259 align:start position:0% option to figure out that the numbers you<00:10:34.049> have<00:10:34.230> multiplied<00:10:34.740> small<00:10:35.639> like<00:10:35.910> they 00:10:36.259 --> 00:10:36.269 align:start position:0% you have multiplied small like they 00:10:36.269 --> 00:10:39.360 align:start position:0% you have multiplied small like they would<00:10:36.569> be<00:10:36.600> 64<00:10:37.529> bits<00:10:37.799> I<00:10:38.040> think<00:10:38.490> it's<00:10:38.670> not<00:10:38.850> worth 00:10:39.360 --> 00:10:39.370 align:start position:0% would be 64 bits I think it's not worth 00:10:39.370 --> 00:10:41.700 align:start position:0% would be 64 bits I think it's not worth to<00:10:39.490> actually<00:10:40.360> handle<00:10:40.930> this<00:10:41.080> case<00:10:41.320> separately 00:10:41.700 --> 00:10:41.710 align:start position:0% to actually handle this case separately 00:10:41.710 --> 00:10:44.790 align:start position:0% to actually handle this case separately because<00:10:42.430> like<00:10:42.790> this<00:10:43.330> top<00:10:43.570> sort<00:10:43.870> of<00:10:44.020> algorithm 00:10:44.790 --> 00:10:44.800 align:start position:0% because like this top sort of algorithm 00:10:44.800 --> 00:10:46.829 align:start position:0% because like this top sort of algorithm and<00:10:45.250> like<00:10:45.460> you<00:10:45.580> have<00:10:45.760> additional<00:10:46.029> conditions 00:10:46.829 --> 00:10:46.839 align:start position:0% and like you have additional conditions 00:10:46.839 --> 00:10:49.680 align:start position:0% and like you have additional conditions and<00:10:47.050> conscious<00:10:47.440> subtract<00:10:48.120> and<00:10:49.120> pretty<00:10:49.480> well 00:10:49.680 --> 00:10:49.690 align:start position:0% and conscious subtract and pretty well 00:10:49.690 --> 00:10:56.610 align:start position:0% and conscious subtract and pretty well pretty<00:10:50.230> much<00:10:50.500> it<00:10:50.650> works<00:10:51.180> great<00:10:52.529> if<00:10:53.529> you<00:10:55.350> if<00:10:56.350> you 00:10:56.610 --> 00:10:56.620 align:start position:0% pretty much it works great if you if you 00:10:56.620 --> 00:11:06.320 align:start position:0% pretty much it works great if you if you just<00:10:57.210> only<00:10:58.210> focus<00:10:58.600> on<00:10:59.220> two<00:11:00.220> five<00:11:00.460> six<00:11:00.790> bits<00:11:04.410> and 00:11:06.320 --> 00:11:06.330 align:start position:0% just only focus on two five six bits and 00:11:06.330 --> 00:11:08.880 align:start position:0% just only focus on two five six bits and the<00:11:07.330> first<00:11:07.600> thing<00:11:07.810> I<00:11:07.960> want<00:11:08.200> to<00:11:08.290> mention<00:11:08.440> here 00:11:08.880 --> 00:11:08.890 align:start position:0% the first thing I want to mention here 00:11:08.890 --> 00:11:12.960 align:start position:0% the first thing I want to mention here is<00:11:09.100> like<00:11:09.960> try<00:11:10.960> first<00:11:11.770> first<00:11:12.250> optimizations 00:11:12.960 --> 00:11:12.970 align:start position:0% is like try first first optimizations 00:11:12.970 --> 00:11:15.269 align:start position:0% is like try first first optimizations you<00:11:13.029> can<00:11:13.240> do<00:11:13.360> is<00:11:13.510> try<00:11:13.690> to<00:11:13.779> avoid<00:11:14.279> dynamic 00:11:15.269 --> 00:11:15.279 align:start position:0% you can do is try to avoid dynamic 00:11:15.279 --> 00:11:17.940 align:start position:0% you can do is try to avoid dynamic memory<00:11:15.460> location<00:11:16.240> so<00:11:16.870> if<00:11:16.990> you<00:11:17.170> use<00:11:17.380> any<00:11:17.650> kind 00:11:17.940 --> 00:11:17.950 align:start position:0% memory location so if you use any kind 00:11:17.950 --> 00:11:23.850 align:start position:0% memory location so if you use any kind of<00:11:18.070> generic<00:11:18.600> multi<00:11:19.680> number<00:11:22.650> library<00:11:23.650> that 00:11:23.850 --> 00:11:23.860 align:start position:0% of generic multi number library that 00:11:23.860 --> 00:11:26.570 align:start position:0% of generic multi number library that actually<00:11:24.010> can<00:11:24.370> have<00:11:24.550> an<00:11:24.730> arbitrary<00:11:25.089> precision 00:11:26.570 --> 00:11:26.580 align:start position:0% actually can have an arbitrary precision 00:11:26.580 --> 00:11:35.329 align:start position:0% actually can have an arbitrary precision which<00:11:27.580> are<00:11:27.730> not<00:11:27.880> fixed<00:11:28.330> on<00:11:28.540> this<00:11:28.779> compile<00:11:29.470> time 00:11:35.329 --> 00:11:35.339 align:start position:0% 00:11:35.339 --> 00:11:45.210 align:start position:0% because<00:11:38.580> the<00:11:39.580> size<00:11:39.820> will<00:11:40.029> be<00:11:42.630> so<00:11:43.920> if<00:11:44.920> this 00:11:45.210 --> 00:11:45.220 align:start position:0% because the size will be so if this 00:11:45.220 --> 00:11:48.000 align:start position:0% because the size will be so if this option<00:11:45.700> to<00:11:45.880> use<00:11:46.060> fixed<00:11:46.510> like<00:11:47.140> fixed<00:11:47.500> position 00:11:48.000 --> 00:11:48.010 align:start position:0% option to use fixed like fixed position 00:11:48.010 --> 00:11:50.579 align:start position:0% option to use fixed like fixed position but<00:11:48.420> this<00:11:49.420> part<00:11:49.720> of<00:11:49.839> it<00:11:49.990> is<00:11:50.110> perfect<00:11:50.529> because 00:11:50.579 --> 00:11:50.589 align:start position:0% but this part of it is perfect because 00:11:50.589 --> 00:11:53.430 align:start position:0% but this part of it is perfect because that's<00:11:51.040> this<00:11:51.220> is<00:11:51.459> the<00:11:51.580> memorial<00:11:51.820> patient<00:11:52.480> some 00:11:53.430 --> 00:11:53.440 align:start position:0% that's this is the memorial patient some 00:11:53.440 --> 00:12:00.800 align:start position:0% that's this is the memorial patient some someone<00:11:53.920> is<00:11:54.220> not<00:11:54.459> for<00:11:54.640> that<00:11:58.170> but<00:11:59.170> I<00:11:59.350> think<00:11:59.650> it's 00:12:00.800 --> 00:12:00.810 align:start position:0% someone is not for that but I think it's 00:12:00.810 --> 00:12:03.870 align:start position:0% someone is not for that but I think it's it's<00:12:01.810> I<00:12:02.440> think<00:12:02.709> we<00:12:02.860> should<00:12:03.040> go<00:12:03.220> further<00:12:03.490> here 00:12:03.870 --> 00:12:03.880 align:start position:0% it's I think we should go further here 00:12:03.880 --> 00:12:08.250 align:start position:0% it's I think we should go further here and<00:12:04.830> also<00:12:05.830> like<00:12:06.160> I<00:12:06.670> am<00:12:07.300> sure<00:12:07.510> I<00:12:07.540> can<00:12:07.750> explain 00:12:08.250 --> 00:12:08.260 align:start position:0% and also like I am sure I can explain 00:12:08.260 --> 00:12:15.710 align:start position:0% and also like I am sure I can explain that<00:12:08.770> with<00:12:09.040> validation<00:12:09.850> but<00:12:12.810> money<00:12:13.810> of<00:12:14.050> the 00:12:15.710 --> 00:12:15.720 align:start position:0% that with validation but money of the 00:12:15.720 --> 00:12:20.330 align:start position:0% that with validation but money of the actually<00:12:16.700> has<00:12:17.700> keep<00:12:18.560> the<00:12:19.560> number<00:12:19.920> of<00:12:19.950> words 00:12:20.330 --> 00:12:20.340 align:start position:0% actually has keep the number of words 00:12:20.340 --> 00:12:24.320 align:start position:0% actually has keep the number of words they<00:12:20.670> were<00:12:20.790> later<00:12:21.360> translated<00:12:22.700> the<00:12:23.700> number<00:12:24.180> of 00:12:24.320 --> 00:12:24.330 align:start position:0% they were later translated the number of 00:12:24.330 --> 00:12:28.930 align:start position:0% they were later translated the number of presentation<00:12:24.930> was<00:12:25.710> a<00:12:25.740> kind<00:12:26.010> of<00:12:27.170> additional 00:12:28.930 --> 00:12:28.940 align:start position:0% presentation was a kind of additional 00:12:28.940 --> 00:12:32.300 align:start position:0% presentation was a kind of additional information<00:12:29.940> stored<00:12:30.270> in<00:12:30.600> the<00:12:30.900> time<00:12:31.310> which 00:12:32.300 --> 00:12:32.310 align:start position:0% information stored in the time which 00:12:32.310 --> 00:12:35.480 align:start position:0% information stored in the time which makes<00:12:32.880> that<00:12:33.150> the<00:12:33.360> type<00:12:33.600> bigger<00:12:34.530> by<00:12:35.430> this 00:12:35.480 --> 00:12:35.490 align:start position:0% makes that the type bigger by this 00:12:35.490 --> 00:12:39.890 align:start position:0% makes that the type bigger by this additional<00:12:36.320> item<00:12:37.320> and<00:12:37.500> actually<00:12:37.920> this<00:12:38.750> so<00:12:39.750> it 00:12:39.890 --> 00:12:39.900 align:start position:0% additional item and actually this so it 00:12:39.900 --> 00:12:42.590 align:start position:0% additional item and actually this so it makes<00:12:40.140> it<00:12:40.320> more<00:12:40.800> isotonic<00:12:41.490> it's<00:12:42.150> out<00:12:42.300> in<00:12:42.480> our 00:12:42.590 --> 00:12:42.600 align:start position:0% makes it more isotonic it's out in our 00:12:42.600 --> 00:12:47.930 align:start position:0% makes it more isotonic it's out in our case<00:12:42.900> methods<00:12:43.380> known<00:12:43.770> as<00:12:43.950> 25%<00:12:44.900> bigger<00:12:45.900> and<00:12:46.940> I 00:12:47.930 --> 00:12:47.940 align:start position:0% case methods known as 25% bigger and I 00:12:47.940 --> 00:12:51.710 align:start position:0% case methods known as 25% bigger and I think<00:12:48.300> from<00:12:48.570> like<00:12:48.780> even<00:12:49.380> the<00:12:50.240> memory<00:12:51.240> access 00:12:51.710 --> 00:12:51.720 align:start position:0% think from like even the memory access 00:12:51.720 --> 00:12:53.990 align:start position:0% think from like even the memory access patterns<00:12:51.870> it's<00:12:52.620> kind<00:12:53.010> of<00:12:53.070> important<00:12:53.700> to<00:12:53.760> not 00:12:53.990 --> 00:12:54.000 align:start position:0% patterns it's kind of important to not 00:12:54.000 --> 00:12:58.010 align:start position:0% patterns it's kind of important to not have<00:12:54.240> it<00:12:54.270> because<00:12:54.930> if<00:12:55.500> you<00:12:55.620> have<00:12:56.660> the<00:12:57.660> minimum 00:12:58.010 --> 00:12:58.020 align:start position:0% have it because if you have the minimum 00:12:58.020 --> 00:13:01.910 align:start position:0% have it because if you have the minimum possible<00:12:58.950> size<00:12:59.490> which<00:13:00.060> is<00:13:00.210> 32<00:13:00.810> bytes<00:13:01.110> it 00:13:01.910 --> 00:13:01.920 align:start position:0% possible size which is 32 bytes it 00:13:01.920 --> 00:13:04.430 align:start position:0% possible size which is 32 bytes it nicely<00:13:02.220> fits<00:13:02.790> into<00:13:03.180> cash<00:13:03.510> buyers<00:13:03.810> and<00:13:04.110> so<00:13:04.290> on 00:13:04.430 --> 00:13:04.440 align:start position:0% nicely fits into cash buyers and so on 00:13:04.440 --> 00:13:07.520 align:start position:0% nicely fits into cash buyers and so on and<00:13:04.770> when<00:13:05.070> you<00:13:05.100> axis<00:13:05.550> start<00:13:06.030> items<00:13:06.450> of<00:13:07.260> this 00:13:07.520 --> 00:13:07.530 align:start position:0% and when you axis start items of this 00:13:07.530 --> 00:13:15.110 align:start position:0% and when you axis start items of this size<00:13:07.800> it's<00:13:08.250> it's<00:13:08.580> performs<00:13:09.120> much<00:13:09.390> faster<00:13:14.120> the 00:13:15.110 --> 00:13:15.120 align:start position:0% size it's it's performs much faster the 00:13:15.120 --> 00:13:19.090 align:start position:0% size it's it's performs much faster the fifth<00:13:16.250> suggestion<00:13:17.250> is<00:13:17.340> try<00:13:17.580> to<00:13:17.840> understand 00:13:19.090 --> 00:13:19.100 align:start position:0% fifth suggestion is try to understand 00:13:19.100 --> 00:13:22.640 align:start position:0% fifth suggestion is try to understand CPU<00:13:20.100> has<00:13:20.970> some<00:13:21.180> kind<00:13:21.420> of<00:13:21.650> special 00:13:22.640 --> 00:13:22.650 align:start position:0% CPU has some kind of special 00:13:22.650 --> 00:13:35.560 align:start position:0% CPU has some kind of special instructions<00:13:24.080> like<00:13:31.880> other<00:13:32.880> operations<00:13:33.630> and 00:13:35.560 --> 00:13:35.570 align:start position:0% instructions like other operations and 00:13:35.570 --> 00:13:46.640 align:start position:0% instructions like other operations and high<00:13:36.570> precision<00:13:36.950> education<00:13:43.820> and<00:13:44.820> think<00:13:45.780> this 00:13:46.640 --> 00:13:46.650 align:start position:0% high precision education and think this 00:13:46.650 --> 00:13:52.490 align:start position:0% high precision education and think this should<00:13:47.310> be<00:13:47.370> aware<00:13:47.700> that<00:13:47.760> when<00:13:48.750> you<00:13:51.440> when<00:13:52.440> you 00:13:52.490 --> 00:13:52.500 align:start position:0% should be aware that when you when you 00:13:52.500 --> 00:13:54.860 align:start position:0% should be aware that when you when you get<00:13:52.710> the<00:13:52.860> counting<00:13:53.460> and<00:13:53.730> high-level<00:13:54.150> language 00:13:54.860 --> 00:13:54.870 align:start position:0% get the counting and high-level language 00:13:54.870 --> 00:13:58.430 align:start position:0% get the counting and high-level language is<00:13:55.470> good<00:13:55.710> to<00:13:55.860> know<00:13:56.010> if<00:13:56.550> I<00:13:56.760> do<00:13:56.880> compiler<00:13:57.450> cookies 00:13:58.430 --> 00:13:58.440 align:start position:0% is good to know if I do compiler cookies 00:13:58.440 --> 00:14:02.060 align:start position:0% is good to know if I do compiler cookies studies<00:13:59.070> by<00:13:59.310> using<00:14:00.050> one<00:14:01.050> of<00:14:01.080> artists<00:14:01.890> how 00:14:02.060 --> 00:14:02.070 align:start position:0% studies by using one of artists how 00:14:02.070 --> 00:14:05.000 align:start position:0% studies by using one of artists how Drax's<00:14:02.580> them<00:14:02.820> or<00:14:03.240> you<00:14:03.750> might<00:14:03.960> need<00:14:04.230> to<00:14:04.560> do<00:14:04.920> some 00:14:05.000 --> 00:14:05.010 align:start position:0% Drax's them or you might need to do some 00:14:05.010 --> 00:14:08.710 align:start position:0% Drax's them or you might need to do some intrinsic<00:14:05.610> stew<00:14:06.110> for<00:14:07.110> example<00:14:07.650> access<00:14:08.190> to 00:14:08.710 --> 00:14:08.720 align:start position:0% intrinsic stew for example access to 00:14:08.720 --> 00:14:17.870 align:start position:0% intrinsic stew for example access to identification<00:14:13.790> and<00:14:15.950> lost<00:14:16.950> being<00:14:17.250> in<00:14:17.700> terms 00:14:17.870 --> 00:14:17.880 align:start position:0% identification and lost being in terms 00:14:17.880 --> 00:14:19.730 align:start position:0% identification and lost being in terms of<00:14:18.120> division<00:14:18.390> I<00:14:18.660> mean<00:14:18.810> I<00:14:19.050> was<00:14:19.560> actually 00:14:19.730 --> 00:14:19.740 align:start position:0% of division I mean I was actually 00:14:19.740 --> 00:14:24.040 align:start position:0% of division I mean I was actually starting<00:14:20.100> a<00:14:20.520> business 00:14:24.040 --> 00:14:24.050 align:start position:0% 00:14:24.050 --> 00:14:26.540 align:start position:0% because<00:14:25.050> I<00:14:25.260> also<00:14:25.530> have<00:14:25.860> to<00:14:26.010> learn<00:14:26.160> most<00:14:26.400> of 00:14:26.540 --> 00:14:26.550 align:start position:0% because I also have to learn most of 00:14:26.550 --> 00:14:31.350 align:start position:0% because I also have to learn most of these 00:14:31.350 --> 00:14:31.360 align:start position:0% 00:14:31.360 --> 00:14:34.049 align:start position:0% and<00:14:31.839> what<00:14:32.739> this<00:14:33.129> paper<00:14:33.459> really<00:14:33.730> taught<00:14:34.029> me 00:14:34.049 --> 00:14:34.059 align:start position:0% and what this paper really taught me 00:14:34.059 --> 00:14:37.679 align:start position:0% and what this paper really taught me here<00:14:34.480> so<00:14:35.019> this<00:14:35.319> is<00:14:35.470> a<00:14:35.499> paper<00:14:36.069> coming<00:14:36.579> from<00:14:36.970> GMP 00:14:37.679 --> 00:14:37.689 align:start position:0% here so this is a paper coming from GMP 00:14:37.689 --> 00:14:45.030 align:start position:0% here so this is a paper coming from GMP library<00:14:38.230> which<00:14:38.679> is<00:14:41.339> regulation<00:14:43.589> it<00:14:44.589> actually 00:14:45.030 --> 00:14:45.040 align:start position:0% library which is regulation it actually 00:14:45.040 --> 00:14:47.460 align:start position:0% library which is regulation it actually gives<00:14:45.610> you<00:14:45.730> like<00:14:45.910> straight<00:14:46.360> away<00:14:46.600> maybe<00:14:47.290> it's 00:14:47.460 --> 00:14:47.470 align:start position:0% gives you like straight away maybe it's 00:14:47.470 --> 00:14:48.900 align:start position:0% gives you like straight away maybe it's not<00:14:47.559> straight<00:14:47.829> away<00:14:47.980> because<00:14:48.399> the<00:14:48.489> form<00:14:48.759> is 00:14:48.900 --> 00:14:48.910 align:start position:0% not straight away because the form is 00:14:48.910 --> 00:14:51.449 align:start position:0% not straight away because the form is it's<00:14:49.480> described<00:14:50.199> in<00:14:50.350> just<00:14:50.559> like<00:14:50.709> mathematical 00:14:51.449 --> 00:14:51.459 align:start position:0% it's described in just like mathematical 00:14:51.459 --> 00:14:53.340 align:start position:0% it's described in just like mathematical form<00:14:51.759> so<00:14:51.939> that<00:14:51.970> you<00:14:52.389> still<00:14:52.629> have<00:14:52.689> to<00:14:52.839> translate 00:14:53.340 --> 00:14:53.350 align:start position:0% form so that you still have to translate 00:14:53.350 --> 00:14:57.119 align:start position:0% form so that you still have to translate it<00:14:53.470> a<00:14:53.709> little<00:14:54.040> code<00:14:54.480> but<00:14:55.480> I<00:14:55.660> think<00:14:55.989> it<00:14:56.139> goes<00:14:56.350> it 00:14:57.119 --> 00:14:57.129 align:start position:0% it a little code but I think it goes it 00:14:57.129 --> 00:14:58.769 align:start position:0% it a little code but I think it goes it gives<00:14:57.489> you<00:14:57.579> almost<00:14:57.730> Felicity<00:14:58.569> how<00:14:58.720> to 00:14:58.769 --> 00:14:58.779 align:start position:0% gives you almost Felicity how to 00:14:58.779 --> 00:15:01.979 align:start position:0% gives you almost Felicity how to actually<00:14:59.049> provide<00:14:59.529> and<00:14:59.949> I<00:15:00.129> didn't<00:15:00.670> still<00:15:01.569> JT 00:15:01.979 --> 00:15:01.989 align:start position:0% actually provide and I didn't still JT 00:15:01.989 --> 00:15:05.910 align:start position:0% actually provide and I didn't still JT is<00:15:02.049> faster<00:15:02.499> here<00:15:03.179> but<00:15:04.179> like<00:15:04.569> knots<00:15:05.199> but<00:15:05.679> by 00:15:05.910 --> 00:15:05.920 align:start position:0% is faster here but like knots but by 00:15:05.920 --> 00:15:09.689 align:start position:0% is faster here but like knots but by some<00:15:06.160> margin<00:15:06.339> because<00:15:06.939> maybe<00:15:07.360> this<00:15:08.699> they 00:15:09.689 --> 00:15:09.699 align:start position:0% some margin because maybe this they 00:15:09.699 --> 00:15:11.900 align:start position:0% some margin because maybe this they definitely<00:15:10.029> use<00:15:10.449> assembly<00:15:11.049> direct<00:15:11.379> another 00:15:11.900 --> 00:15:11.910 align:start position:0% definitely use assembly direct another 00:15:11.910 --> 00:15:15.389 align:start position:0% definitely use assembly direct another oil<00:15:12.910> speed-up<00:15:13.540> so<00:15:14.470> maybe<00:15:14.739> this<00:15:15.009> is<00:15:15.069> like 00:15:15.389 --> 00:15:15.399 align:start position:0% oil speed-up so maybe this is like 00:15:15.399 --> 00:15:24.859 align:start position:0% oil speed-up so maybe this is like somehow<00:15:16.209> compiler<00:15:16.839> for<00:15:17.199> that<00:15:17.529> is<00:15:17.679> chaotic 00:15:24.859 --> 00:15:24.869 align:start position:0% 00:15:24.869 --> 00:15:27.869 align:start position:0% optimize<00:15:25.869> the<00:15:26.199> same<00:15:26.439> way<00:15:26.619> like<00:15:27.279> something<00:15:27.730> you 00:15:27.869 --> 00:15:27.879 align:start position:0% optimize the same way like something you 00:15:27.879 --> 00:15:33.410 align:start position:0% optimize the same way like something you did<00:15:28.089> some<00:15:28.360> time<00:15:28.389> ago 00:15:33.410 --> 00:15:33.420 align:start position:0% 00:15:33.420 --> 00:15:36.540 align:start position:0% but<00:15:34.420> if<00:15:34.720> you<00:15:34.959> like<00:15:35.260> still<00:15:35.950> lost 00:15:36.540 --> 00:15:36.550 align:start position:0% but if you like still lost 00:15:36.550 --> 00:15:39.420 align:start position:0% but if you like still lost so<00:15:36.790> my<00:15:37.209> suggestion<00:15:37.690> is<00:15:37.930> that<00:15:37.959> you<00:15:38.200> because<00:15:38.920> the 00:15:39.420 --> 00:15:39.430 align:start position:0% so my suggestion is that you because the 00:15:39.430 --> 00:15:43.350 align:start position:0% so my suggestion is that you because the compiler<00:15:39.970> options<00:15:40.649> try<00:15:41.649> to<00:15:41.709> support<00:15:42.370> de<00:15:43.209> my 00:15:43.350 --> 00:15:43.360 align:start position:0% compiler options try to support de my 00:15:43.360 --> 00:15:47.220 align:start position:0% compiler options try to support de my device<00:15:43.839> called<00:15:44.080> Holocaust<00:15:44.830> week<00:15:45.820> it<00:15:46.420> will<00:15:46.600> ya 00:15:47.220 --> 00:15:47.230 align:start position:0% device called Holocaust week it will ya 00:15:47.230 --> 00:15:48.680 align:start position:0% device called Holocaust week it will ya sports<00:15:47.829> the<00:15:47.980> license<00:15:48.370> on<00:15:48.459> it 00:15:48.680 --> 00:15:48.690 align:start position:0% sports the license on it 00:15:48.690 --> 00:15:54.480 align:start position:0% sports the license on it it's<00:15:49.690> apache2<00:15:52.019> so<00:15:53.019> I<00:15:53.260> mean<00:15:53.529> by<00:15:53.920> talking<00:15:54.190> I 00:15:54.480 --> 00:15:54.490 align:start position:0% it's apache2 so I mean by talking I 00:15:54.490 --> 00:15:57.509 align:start position:0% it's apache2 so I mean by talking I don't<00:15:54.940> mean<00:15:55.089> use<00:15:55.420> it<00:15:55.570> in<00:15:55.690> the<00:15:55.810> basic<00:15:56.339> in<00:15:57.339> this 00:15:57.509 --> 00:15:57.519 align:start position:0% don't mean use it in the basic in this 00:15:57.519 --> 00:16:03.889 align:start position:0% don't mean use it in the basic in this case<00:15:57.850> is<00:15:58.149> on<00:15:58.390> this<00:15:58.570> accessing<00:15:59.560> see<00:15:59.829> called 00:16:03.889 --> 00:16:03.899 align:start position:0% 00:16:03.899 --> 00:16:07.949 align:start position:0% public<00:16:04.899> enjoy<00:16:05.230> that<00:16:06.209> by<00:16:07.209> holding<00:16:07.450> I<00:16:07.720> mean<00:16:07.870> you 00:16:07.949 --> 00:16:07.959 align:start position:0% public enjoy that by holding I mean you 00:16:07.959 --> 00:16:31.470 align:start position:0% public enjoy that by holding I mean you can<00:16:08.170> try<00:16:08.380> to<00:16:13.200> see<00:16:20.700> ya 00:16:31.470 --> 00:16:31.480 align:start position:0% 00:16:31.480 --> 00:17:34.830 align:start position:0% [Music] 00:17:34.830 --> 00:17:34.840 align:start position:0% 00:17:34.840 --> 00:17:49.620 align:start position:0% [Music] 00:17:49.620 --> 00:17:49.630 align:start position:0% 00:17:49.630 --> 00:18:00.000 align:start position:0% [Music] 00:18:00.000 --> 00:18:00.010 align:start position:0% 00:18:00.010 --> 00:18:16.540 align:start position:0% so<00:18:12.580> at<00:18:13.960> IBM<00:18:14.960> we<00:18:15.380> actually<00:18:15.800> put<00:18:16.220> a<00:18:16.250> bit<00:18:16.520> more 00:18:16.540 --> 00:18:16.550 align:start position:0% so at IBM we actually put a bit more 00:18:16.550 --> 00:18:18.360 align:start position:0% so at IBM we actually put a bit more work<00:18:17.060> in 00:18:18.360 --> 00:18:18.370 align:start position:0% work in 00:18:18.370 --> 00:18:21.970 align:start position:0% work in presenting<00:18:19.370> price<00:18:20.080> before<00:18:21.080> the<00:18:21.320> institution 00:18:21.970 --> 00:18:21.980 align:start position:0% presenting price before the institution 00:18:21.980 --> 00:18:26.740 align:start position:0% presenting price before the institution spots<00:18:23.650> so<00:18:24.650> I<00:18:25.010> would<00:18:25.670> try<00:18:25.790> to<00:18:25.880> explain<00:18:26.330> that<00:18:26.510> by 00:18:26.740 --> 00:18:26.750 align:start position:0% spots so I would try to explain that by 00:18:26.750 --> 00:18:29.580 align:start position:0% spots so I would try to explain that by example<00:18:27.320> so<00:18:27.350> we<00:18:27.710> have<00:18:27.890> a<00:18:27.920> called 00:18:29.580 --> 00:18:29.590 align:start position:0% example so we have a called 00:18:29.590 --> 00:18:34.300 align:start position:0% example so we have a called TV<00:18:30.590> and<00:18:30.740> byte<00:18:31.010> code<00:18:31.340> us<00:18:31.550> a<00:18:31.760> video<00:18:33.130> but<00:18:34.130> you 00:18:34.300 --> 00:18:34.310 align:start position:0% TV and byte code us a video but you 00:18:34.310 --> 00:18:35.830 align:start position:0% TV and byte code us a video but you don't<00:18:34.580> actually<00:18:34.760> need<00:18:35.000> to<00:18:35.060> understand<00:18:35.660> what 00:18:35.830 --> 00:18:35.840 align:start position:0% don't actually need to understand what 00:18:35.840 --> 00:18:36.400 align:start position:0% don't actually need to understand what it<00:18:35.960> does 00:18:36.400 --> 00:18:36.410 align:start position:0% it does 00:18:36.410 --> 00:18:40.570 align:start position:0% it does actually<00:18:36.830> I'd<00:18:37.180> like<00:18:38.180> do<00:18:38.810> something<00:18:39.430> in<00:18:40.430> the 00:18:40.570 --> 00:18:40.580 align:start position:0% actually I'd like do something in the 00:18:40.580 --> 00:18:43.600 align:start position:0% actually I'd like do something in the end<00:18:40.700> this<00:18:41.390> one<00:18:41.840> is<00:18:42.020> thank<00:18:42.260> you<00:18:42.410> so<00:18:42.770> it's 00:18:43.600 --> 00:18:43.610 align:start position:0% end this one is thank you so it's 00:18:43.610 --> 00:18:48.340 align:start position:0% end this one is thank you so it's actually<00:18:43.790> pretty<00:18:44.450> stupid<00:18:44.870> now<00:18:46.150> anyway<00:18:47.350> what 00:18:48.340 --> 00:18:48.350 align:start position:0% actually pretty stupid now anyway what 00:18:48.350 --> 00:18:51.070 align:start position:0% actually pretty stupid now anyway what we<00:18:48.470> want<00:18:48.650> to<00:18:48.800> do<00:18:48.980> and<00:18:49.940> we<00:18:50.150> will<00:18:50.330> try<00:18:50.570> to<00:18:50.600> do<00:18:50.900> it 00:18:51.070 --> 00:18:51.080 align:start position:0% we want to do and we will try to do it 00:18:51.080 --> 00:18:56.920 align:start position:0% we want to do and we will try to do it what's<00:18:52.990> step<00:18:53.990> is<00:18:54.140> doing<00:18:54.320> in<00:18:55.220> one<00:18:55.630> so<00:18:56.630> we<00:18:56.750> want 00:18:56.920 --> 00:18:56.930 align:start position:0% what's step is doing in one so we want 00:18:56.930 --> 00:19:00.250 align:start position:0% what's step is doing in one so we want to<00:18:57.110> identify<00:18:57.710> a<00:18:58.460> jukebox<00:18:58.730> baby<00:18:59.210> blocks<00:18:59.930> are 00:19:00.250 --> 00:19:00.260 align:start position:0% to identify a jukebox baby blocks are 00:19:00.260 --> 00:19:08.860 align:start position:0% to identify a jukebox baby blocks are the<00:19:01.220> sequence<00:19:01.820> of<00:19:01.940> code<00:19:02.270> kind<00:19:03.110> of<00:19:06.370> and<00:19:07.870> this 00:19:08.860 --> 00:19:08.870 align:start position:0% the sequence of code kind of and this 00:19:08.870 --> 00:19:10.900 align:start position:0% the sequence of code kind of and this coming<00:19:09.260> from<00:19:09.440> the<00:19:09.680> compiler<00:19:10.550> construction 00:19:10.900 --> 00:19:10.910 align:start position:0% coming from the compiler construction 00:19:10.910 --> 00:19:14.950 align:start position:0% coming from the compiler construction and<00:19:11.530> basic<00:19:12.530> doors<00:19:12.740> are<00:19:12.950> there<00:19:13.630> the<00:19:14.630> sequence 00:19:14.950 --> 00:19:14.960 align:start position:0% and basic doors are there the sequence 00:19:14.960 --> 00:19:17.470 align:start position:0% and basic doors are there the sequence of<00:19:15.020> vegetation<00:19:15.410> that<00:19:15.680> for<00:19:16.610> sure<00:19:16.790> executed<00:19:17.390> in 00:19:17.470 --> 00:19:17.480 align:start position:0% of vegetation that for sure executed in 00:19:17.480 --> 00:19:19.590 align:start position:0% of vegetation that for sure executed in the<00:19:17.570> order<00:19:17.630> and 00:19:19.590 --> 00:19:19.600 align:start position:0% the order and 00:19:19.600 --> 00:19:40.180 align:start position:0% the order and [Music] 00:19:40.180 --> 00:19:40.190 align:start position:0% 00:19:40.190 --> 00:19:46.490 align:start position:0% [Music] 00:19:46.490 --> 00:19:46.500 align:start position:0% 00:19:46.500 --> 00:21:02.519 align:start position:0% so 00:21:02.519 --> 00:21:02.529 align:start position:0% 00:21:02.529 --> 00:21:07.570 align:start position:0% what<00:21:03.529> we<00:21:03.679> do<00:21:03.830> here<00:21:04.129> we<00:21:04.789> actually<00:21:05.679> have<00:21:06.679> a 00:21:07.570 --> 00:21:07.580 align:start position:0% what we do here we actually have a 00:21:07.580 --> 00:21:09.849 align:start position:0% what we do here we actually have a 20-block<00:21:08.149> we<00:21:08.450> can<00:21:08.629> pick<00:21:08.989> up<00:21:09.139> the<00:21:09.710> bass 00:21:09.849 --> 00:21:09.859 align:start position:0% 20-block we can pick up the bass 00:21:09.859 --> 00:21:16.379 align:start position:0% 20-block we can pick up the bass customer<00:21:10.429> satisfactions<00:21:11.980> but<00:21:12.980> you<00:21:13.159> can<00:21:13.309> also 00:21:16.379 --> 00:21:16.389 align:start position:0% 00:21:16.389 --> 00:21:29.379 align:start position:0% pre-computer<00:21:17.389> some<00:21:21.999> heavy<00:21:28.389> drinking 00:21:29.379 --> 00:21:29.389 align:start position:0% pre-computer some heavy drinking 00:21:29.389 --> 00:21:31.479 align:start position:0% pre-computer some heavy drinking execution<00:21:29.960> we<00:21:30.109> can<00:21:30.289> check<00:21:30.529> this<00:21:30.919> conditions 00:21:31.479 --> 00:21:31.489 align:start position:0% execution we can check this conditions 00:21:31.489 --> 00:21:40.769 align:start position:0% execution we can check this conditions on<00:21:31.730> in<00:21:31.909> pervasive<00:21:32.509> blog<00:21:32.720> and<00:21:34.179> any<00:21:35.179> more 00:21:40.769 --> 00:21:40.779 align:start position:0% 00:21:40.779 --> 00:21:43.810 align:start position:0% information<00:21:41.779> because<00:21:42.559> we<00:21:42.859> give<00:21:43.190> information 00:21:43.810 --> 00:21:43.820 align:start position:0% information because we give information 00:21:43.820 --> 00:21:46.629 align:start position:0% information because we give information and<00:21:44.739> we<00:21:45.739> don't<00:21:45.919> have<00:21:46.070> to<00:21:46.159> check<00:21:46.309> it<00:21:46.460> for 00:21:46.629 --> 00:21:46.639 align:start position:0% and we don't have to check it for 00:21:46.639 --> 00:22:07.800 align:start position:0% and we don't have to check it for ratings 00:22:07.800 --> 00:22:07.810 align:start position:0% 00:22:07.810 --> 00:22:26.340 align:start position:0% [Music] 00:22:26.340 --> 00:22:26.350 align:start position:0% 00:22:26.350 --> 00:22:42.010 align:start position:0% between<00:22:27.350> the 00:22:42.010 --> 00:22:42.020 align:start position:0% 00:22:42.020 --> 00:22:50.350 align:start position:0% [Applause] 00:22:50.350 --> 00:22:50.360 align:start position:0% 00:22:50.360 --> 00:22:52.420 align:start position:0% you