1 00:00:01,100 --> 00:00:04,519 covering the week's top textbooks like 2 00:00:04,519 --> 00:00:04,529 covering the week's top textbooks like 3 00:00:04,529 --> 00:00:07,940 covering the week's top textbooks like Linux bias the latest experimental 4 00:00:07,940 --> 00:00:07,950 Linux bias the latest experimental 5 00:00:07,950 --> 00:00:10,100 Linux bias the latest experimental addition to the Chrome browser promises 6 00:00:10,100 --> 00:00:10,110 addition to the Chrome browser promises 7 00:00:10,110 --> 00:00:13,850 addition to the Chrome browser promises to save a ton of power usage a new flag 8 00:00:13,850 --> 00:00:13,860 to save a ton of power usage a new flag 9 00:00:13,860 --> 00:00:15,740 to save a ton of power usage a new flag in the canary version of chrome called 10 00:00:15,740 --> 00:00:15,750 in the canary version of chrome called 11 00:00:15,750 --> 00:00:18,109 in the canary version of chrome called throttle javascript timers in background 12 00:00:18,109 --> 00:00:18,119 throttle javascript timers in background 13 00:00:18,119 --> 00:00:20,090 throttle javascript timers in background will cut down on the processing that 14 00:00:20,090 --> 00:00:20,100 will cut down on the processing that 15 00:00:20,100 --> 00:00:22,250 will cut down on the processing that normally happens in background tabs and 16 00:00:22,250 --> 00:00:22,260 normally happens in background tabs and 17 00:00:22,260 --> 00:00:25,250 normally happens in background tabs and it could add two hours to a laptop's 18 00:00:25,250 --> 00:00:25,260 it could add two hours to a laptop's 19 00:00:25,260 --> 00:00:28,820 it could add two hours to a laptop's runtime JavaScript's timers often track 20 00:00:28,820 --> 00:00:28,830 runtime JavaScript's timers often track 21 00:00:28,830 --> 00:00:30,470 runtime JavaScript's timers often track user interaction with a web page 22 00:00:30,470 --> 00:00:30,480 user interaction with a web page 23 00:00:30,480 --> 00:00:32,630 user interaction with a web page checking things like the scroll position 24 00:00:32,630 --> 00:00:32,640 checking things like the scroll position 25 00:00:32,640 --> 00:00:34,910 checking things like the scroll position and add interaction while the tab is 26 00:00:34,910 --> 00:00:34,920 and add interaction while the tab is 27 00:00:34,920 --> 00:00:37,340 and add interaction while the tab is open this also happens on background 28 00:00:37,340 --> 00:00:37,350 open this also happens on background 29 00:00:37,350 --> 00:00:39,799 open this also happens on background tabs which really isn't useful since by 30 00:00:39,799 --> 00:00:39,809 tabs which really isn't useful since by 31 00:00:39,809 --> 00:00:41,990 tabs which really isn't useful since by definition a background tab isn't being 32 00:00:41,990 --> 00:00:42,000 definition a background tab isn't being 33 00:00:42,000 --> 00:00:44,510 definition a background tab isn't being interacted with when you have a bunch of 34 00:00:44,510 --> 00:00:44,520 interacted with when you have a bunch of 35 00:00:44,520 --> 00:00:46,340 interacted with when you have a bunch of tabs open these timers can chew through 36 00:00:46,340 --> 00:00:46,350 tabs open these timers can chew through 37 00:00:46,350 --> 00:00:49,330 tabs open these timers can chew through a good amount of battery for no reason 38 00:00:49,330 --> 00:00:49,340 a good amount of battery for no reason 39 00:00:49,340 --> 00:00:51,799 a good amount of battery for no reason normally background tabs can trigger a 40 00:00:51,799 --> 00:00:51,809 normally background tabs can trigger a 41 00:00:51,809 --> 00:00:55,430 normally background tabs can trigger a wake-up once per second now in canary if 42 00:00:55,430 --> 00:00:55,440 wake-up once per second now in canary if 43 00:00:55,440 --> 00:00:57,410 wake-up once per second now in canary if you turn on the new throttle JavaScript 44 00:00:57,410 --> 00:00:57,420 you turn on the new throttle JavaScript 45 00:00:57,420 --> 00:01:00,020 you turn on the new throttle JavaScript timer setting any tab that is being in 46 00:01:00,020 --> 00:01:00,030 timer setting any tab that is being in 47 00:01:00,030 --> 00:01:01,220 timer setting any tab that is being in the background for more than five 48 00:01:01,220 --> 00:01:01,230 the background for more than five 49 00:01:01,230 --> 00:01:03,410 the background for more than five minutes we'll have these timers disabled 50 00:01:03,410 --> 00:01:03,420 minutes we'll have these timers disabled 51 00:01:03,420 --> 00:01:07,090 minutes we'll have these timers disabled with wake-ups limited to once per minute 52 00:01:07,090 --> 00:01:07,100 with wake-ups limited to once per minute 53 00:01:07,100 --> 00:01:10,460 with wake-ups limited to once per minute Google Ransom - sorry Google ran some 54 00:01:10,460 --> 00:01:10,470 Google Ransom - sorry Google ran some 55 00:01:10,470 --> 00:01:12,890 Google Ransom - sorry Google ran some tests to see what kind of impact this 56 00:01:12,890 --> 00:01:12,900 tests to see what kind of impact this 57 00:01:12,900 --> 00:01:15,200 tests to see what kind of impact this would have on battery life for the first 58 00:01:15,200 --> 00:01:15,210 would have on battery life for the first 59 00:01:15,210 --> 00:01:18,469 would have on battery life for the first test they used a 20-18 15-inch MacBook 60 00:01:18,469 --> 00:01:18,479 test they used a 20-18 15-inch MacBook 61 00:01:18,479 --> 00:01:22,039 test they used a 20-18 15-inch MacBook Pro and loaded up 36 background tabs 62 00:01:22,039 --> 00:01:22,049 Pro and loaded up 36 background tabs 63 00:01:22,049 --> 00:01:24,710 Pro and loaded up 36 background tabs with a blank foreground tab then let the 64 00:01:24,710 --> 00:01:24,720 with a blank foreground tab then let the 65 00:01:24,720 --> 00:01:27,530 with a blank foreground tab then let the laptop run until it died but the feature 66 00:01:27,530 --> 00:01:27,540 laptop run until it died but the feature 67 00:01:27,540 --> 00:01:29,990 laptop run until it died but the feature turned on the laptop lasted two hours 68 00:01:29,990 --> 00:01:30,000 turned on the laptop lasted two hours 69 00:01:30,000 --> 00:01:33,380 turned on the laptop lasted two hours longer or 28% longer than the default 70 00:01:33,380 --> 00:01:33,390 longer or 28% longer than the default 71 00:01:33,390 --> 00:01:35,899 longer or 28% longer than the default settings that's a huge improvement and 72 00:01:35,899 --> 00:01:35,909 settings that's a huge improvement and 73 00:01:35,909 --> 00:01:37,550 settings that's a huge improvement and it still can't get croup but it still 74 00:01:37,550 --> 00:01:37,560 it still can't get croup but it still 75 00:01:37,560 --> 00:01:39,080 it still can't get croup but it still can't get chrome up to the level of 76 00:01:39,080 --> 00:01:39,090 can't get chrome up to the level of 77 00:01:39,090 --> 00:01:41,719 can't get chrome up to the level of Apple's Safari which bested Chrome by 78 00:01:41,719 --> 00:01:41,729 Apple's Safari which bested Chrome by 79 00:01:41,729 --> 00:01:43,399 Apple's Safari which bested Chrome by three hours with the default settings 80 00:01:43,399 --> 00:01:43,409 three hours with the default settings 81 00:01:43,409 --> 00:01:45,920 three hours with the default settings and by one hour with the new throttling 82 00:01:45,920 --> 00:01:45,930 and by one hour with the new throttling 83 00:01:45,930 --> 00:01:48,980 and by one hour with the new throttling flag the first test showed just how much 84 00:01:48,980 --> 00:01:48,990 flag the first test showed just how much 85 00:01:48,990 --> 00:01:50,600 flag the first test showed just how much power can be sucked up by background 86 00:01:50,600 --> 00:01:50,610 power can be sucked up by background 87 00:01:50,610 --> 00:01:53,060 power can be sucked up by background tabs but the next test was more of a 88 00:01:53,060 --> 00:01:53,070 tabs but the next test was more of a 89 00:01:53,070 --> 00:01:56,120 tabs but the next test was more of a real-world use case it swapped out of 90 00:01:56,120 --> 00:01:56,130 real-world use case it swapped out of 91 00:01:56,130 --> 00:01:58,069 real-world use case it swapped out of the blank foreground tab for a YouTube 92 00:01:58,069 --> 00:01:58,079 the blank foreground tab for a YouTube 93 00:01:58,079 --> 00:02:00,260 the blank foreground tab for a YouTube video with an actual foreground task 94 00:02:00,260 --> 00:02:00,270 video with an actual foreground task 95 00:02:00,270 --> 00:02:01,850 video with an actual foreground task going on the difference was less 96 00:02:01,850 --> 00:02:01,860 going on the difference was less 97 00:02:01,860 --> 00:02:04,520 going on the difference was less dramatic but still significant without 98 00:02:04,520 --> 00:02:04,530 dramatic but still significant without 99 00:02:04,530 --> 00:02:06,740 dramatic but still significant without throttling tabs chrome lasted four point 100 00:02:06,740 --> 00:02:06,750 throttling tabs chrome lasted four point 101 00:02:06,750 --> 00:02:09,320 throttling tabs chrome lasted four point seven hours and with throttling it got 102 00:02:09,320 --> 00:02:09,330 seven hours and with throttling it got 103 00:02:09,330 --> 00:02:12,290 seven hours and with throttling it got an extra thirty nine minutes lasting 5.3 104 00:02:12,290 --> 00:02:12,300 an extra thirty nine minutes lasting 5.3 105 00:02:12,300 --> 00:02:12,890 an extra thirty nine minutes lasting 5.3 hours 106 00:02:12,890 --> 00:02:12,900 hours 107 00:02:12,900 --> 00:02:15,589 hours safari was not included in the second 108 00:02:15,589 --> 00:02:15,599 safari was not included in the second 109 00:02:15,599 --> 00:02:18,140 safari was not included in the second test while these are promising results 110 00:02:18,140 --> 00:02:18,150 test while these are promising results 111 00:02:18,150 --> 00:02:19,309 test while these are promising results Google says they are still investigating 112 00:02:19,309 --> 00:02:19,319 Google says they are still investigating 113 00:02:19,319 --> 00:02:21,860 Google says they are still investigating how limiting background timers will 114 00:02:21,860 --> 00:02:21,870 how limiting background timers will 115 00:02:21,870 --> 00:02:24,649 how limiting background timers will affect web pages while Google says that 116 00:02:24,649 --> 00:02:24,659 affect web pages while Google says that 117 00:02:24,659 --> 00:02:26,179 affect web pages while Google says that the work done from these JavaScript 118 00:02:26,179 --> 00:02:26,189 the work done from these JavaScript 119 00:02:26,189 --> 00:02:28,520 the work done from these JavaScript timers was often not valuable to the 120 00:02:28,520 --> 00:02:28,530 timers was often not valuable to the 121 00:02:28,530 --> 00:02:30,199 timers was often not valuable to the user when the page was in the background 122 00:02:30,199 --> 00:02:30,209 user when the page was in the background 123 00:02:30,209 --> 00:02:32,420 user when the page was in the background they also don't want to break web pages 124 00:02:32,420 --> 00:02:32,430 they also don't want to break web pages 125 00:02:32,430 --> 00:02:34,190 they also don't want to break web pages which provide valuable background 126 00:02:34,190 --> 00:02:34,200 which provide valuable background 127 00:02:34,200 --> 00:02:36,830 which provide valuable background services like incoming chat and video 128 00:02:36,830 --> 00:02:36,840 services like incoming chat and video 129 00:02:36,840 --> 00:02:39,130 services like incoming chat and video messages media playback and 130 00:02:39,130 --> 00:02:39,140 messages media playback and 131 00:02:39,140 --> 00:02:41,110 messages media playback and notifications 132 00:02:41,110 --> 00:02:41,120 notifications 133 00:02:41,120 --> 00:02:44,000 notifications after a 50% roll out on the canary 134 00:02:44,000 --> 00:02:44,010 after a 50% roll out on the canary 135 00:02:44,010 --> 00:02:45,740 after a 50% roll out on the canary version google plans to gather feedback 136 00:02:45,740 --> 00:02:45,750 version google plans to gather feedback 137 00:02:45,750 --> 00:02:48,080 version google plans to gather feedback from web developers before the change 138 00:02:48,080 --> 00:02:48,090 from web developers before the change 139 00:02:48,090 --> 00:02:51,080 from web developers before the change hits the wider chrome user base you know 140 00:02:51,080 --> 00:02:51,090 hits the wider chrome user base you know 141 00:02:51,090 --> 00:02:53,479 hits the wider chrome user base you know that's an interesting story because for 142 00:02:53,479 --> 00:02:53,489 that's an interesting story because for 143 00:02:53,489 --> 00:02:57,110 that's an interesting story because for my wife and I were both Chrome users we 144 00:02:57,110 --> 00:02:57,120 my wife and I were both Chrome users we 145 00:02:57,120 --> 00:02:59,960 my wife and I were both Chrome users we often have a ton of tabs open I mean if 146 00:02:59,960 --> 00:02:59,970 often have a ton of tabs open I mean if 147 00:02:59,970 --> 00:03:03,259 often have a ton of tabs open I mean if I'm doing you know research for work or 148 00:03:03,259 --> 00:03:03,269 I'm doing you know research for work or 149 00:03:03,269 --> 00:03:05,599 I'm doing you know research for work or she's doing you know different things at 150 00:03:05,599 --> 00:03:05,609 she's doing you know different things at 151 00:03:05,609 --> 00:03:06,770 she's doing you know different things at home or we're helping the kids with 152 00:03:06,770 --> 00:03:06,780 home or we're helping the kids with 153 00:03:06,780 --> 00:03:09,170 home or we're helping the kids with school between their schoolwork and and 154 00:03:09,170 --> 00:03:09,180 school between their schoolwork and and 155 00:03:09,180 --> 00:03:11,420 school between their schoolwork and and the research that they're doing and the 156 00:03:11,420 --> 00:03:11,430 the research that they're doing and the 157 00:03:11,430 --> 00:03:12,649 the research that they're doing and the the work that they're working on on 158 00:03:12,649 --> 00:03:12,659 the work that they're working on on 159 00:03:12,659 --> 00:03:14,690 the work that they're working on on their Google Docs we could at any point 160 00:03:14,690 --> 00:03:14,700 their Google Docs we could at any point 161 00:03:14,700 --> 00:03:17,449 their Google Docs we could at any point have a couple dozen tabs open and I mean 162 00:03:17,449 --> 00:03:17,459 have a couple dozen tabs open and I mean 163 00:03:17,459 --> 00:03:20,330 have a couple dozen tabs open and I mean the with Mike with our family computer 164 00:03:20,330 --> 00:03:20,340 the with Mike with our family computer 165 00:03:20,340 --> 00:03:22,819 the with Mike with our family computer we've got the dual monitors and it's not 166 00:03:22,819 --> 00:03:22,829 we've got the dual monitors and it's not 167 00:03:22,829 --> 00:03:25,789 we've got the dual monitors and it's not uncommon for me to have a browser off to 168 00:03:25,789 --> 00:03:25,799 uncommon for me to have a browser off to 169 00:03:25,799 --> 00:03:29,780 uncommon for me to have a browser off to the one screen with two dozen tabs and 170 00:03:29,780 --> 00:03:29,790 the one screen with two dozen tabs and 171 00:03:29,790 --> 00:03:32,569 the one screen with two dozen tabs and then my main screen where I've got a 172 00:03:32,569 --> 00:03:32,579 then my main screen where I've got a 173 00:03:32,579 --> 00:03:35,539 then my main screen where I've got a couple of main tabs and so to have an 174 00:03:35,539 --> 00:03:35,549 couple of main tabs and so to have an 175 00:03:35,549 --> 00:03:37,520 couple of main tabs and so to have an ANA grant it's not a laptop but to have 176 00:03:37,520 --> 00:03:37,530 ANA grant it's not a laptop but to have 177 00:03:37,530 --> 00:03:42,020 ANA grant it's not a laptop but to have that power saving is huge because not 178 00:03:42,020 --> 00:03:42,030 that power saving is huge because not 179 00:03:42,030 --> 00:03:44,750 that power saving is huge because not only is it less power on the computer 180 00:03:44,750 --> 00:03:44,760 only is it less power on the computer 181 00:03:44,760 --> 00:03:46,610 only is it less power on the computer that's being used but over time you 182 00:03:46,610 --> 00:03:46,620 that's being used but over time you 183 00:03:46,620 --> 00:03:48,530 that's being used but over time you could see some savings and you're sure 184 00:03:48,530 --> 00:03:48,540 could see some savings and you're sure 185 00:03:48,540 --> 00:03:50,360 could see some savings and you're sure you know you mentioned it's not a laptop 186 00:03:50,360 --> 00:03:50,370 you know you mentioned it's not a laptop 187 00:03:50,370 --> 00:03:52,250 you know you mentioned it's not a laptop and and one of the things that Beckett 188 00:03:52,250 --> 00:03:52,260 and and one of the things that Beckett 189 00:03:52,260 --> 00:03:54,409 and and one of the things that Beckett didn't touch on Jeff was performance 190 00:03:54,409 --> 00:03:54,419 didn't touch on Jeff was performance 191 00:03:54,419 --> 00:03:56,839 didn't touch on Jeff was performance yeah and I do think about how even on 192 00:03:56,839 --> 00:03:56,849 yeah and I do think about how even on 193 00:03:56,849 --> 00:04:00,289 yeah and I do think about how even on our desktop computer at home my youngest 194 00:04:00,289 --> 00:04:00,299 our desktop computer at home my youngest 195 00:04:00,299 --> 00:04:03,379 our desktop computer at home my youngest will have that same scenario 20 tabs 196 00:04:03,379 --> 00:04:03,389 will have that same scenario 20 tabs 197 00:04:03,389 --> 00:04:07,879 will have that same scenario 20 tabs open and then he'll switch user oh right 198 00:04:07,879 --> 00:04:07,889 open and then he'll switch user oh right 199 00:04:07,889 --> 00:04:11,780 open and then he'll switch user oh right so which is great because Linux Mint 200 00:04:11,780 --> 00:04:11,790 so which is great because Linux Mint 201 00:04:11,790 --> 00:04:13,729 so which is great because Linux Mint allows us to have multiple people logged 202 00:04:13,729 --> 00:04:13,739 allows us to have multiple people logged 203 00:04:13,739 --> 00:04:15,979 allows us to have multiple people logged in at once but now we've got somebody 204 00:04:15,979 --> 00:04:15,989 in at once but now we've got somebody 205 00:04:15,989 --> 00:04:19,279 in at once but now we've got somebody else logging in and double tops yeah so 206 00:04:19,279 --> 00:04:19,289 else logging in and double tops yeah so 207 00:04:19,289 --> 00:04:21,709 else logging in and double tops yeah so his Java JavaScript timers are still 208 00:04:21,709 --> 00:04:21,719 his Java JavaScript timers are still 209 00:04:21,719 --> 00:04:24,690 his Java JavaScript timers are still going off in his browser on his profile 210 00:04:24,690 --> 00:04:24,700 going off in his browser on his profile 211 00:04:24,700 --> 00:04:27,450 going off in his browser on his profile yes so I wonder how it would affect 212 00:04:27,450 --> 00:04:27,460 yes so I wonder how it would affect 213 00:04:27,460 --> 00:04:29,910 yes so I wonder how it would affect performance as well yeah I I'm very 214 00:04:29,910 --> 00:04:29,920 performance as well yeah I I'm very 215 00:04:29,920 --> 00:04:32,220 performance as well yeah I I'm very interested to see I mean I I know it's a 216 00:04:32,220 --> 00:04:32,230 interested to see I mean I I know it's a 217 00:04:32,230 --> 00:04:35,040 interested to see I mean I I know it's a small change yeah going from one second 218 00:04:35,040 --> 00:04:35,050 small change yeah going from one second 219 00:04:35,050 --> 00:04:38,250 small change yeah going from one second to the one-minute but I'm really looking 220 00:04:38,250 --> 00:04:38,260 to the one-minute but I'm really looking 221 00:04:38,260 --> 00:04:40,890 to the one-minute but I'm really looking forward to see the impact because I do 222 00:04:40,890 --> 00:04:40,900 forward to see the impact because I do 223 00:04:40,900 --> 00:04:44,910 forward to see the impact because I do think it's gonna be it will have that 224 00:04:44,910 --> 00:04:44,920 think it's gonna be it will have that 225 00:04:44,920 --> 00:04:46,920 think it's gonna be it will have that you know performance power but and 226 00:04:46,920 --> 00:04:46,930 you know performance power but and 227 00:04:46,930 --> 00:04:49,800 you know performance power but and especially for older devices like if you 228 00:04:49,800 --> 00:04:49,810 especially for older devices like if you 229 00:04:49,810 --> 00:04:51,540 especially for older devices like if you if you've got an older laptop that's 230 00:04:51,540 --> 00:04:51,550 if you've got an older laptop that's 231 00:04:51,550 --> 00:04:53,490 if you've got an older laptop that's always struggling I mean not just 232 00:04:53,490 --> 00:04:53,500 always struggling I mean not just 233 00:04:53,500 --> 00:04:55,920 always struggling I mean not just battery saving but if it does improve 234 00:04:55,920 --> 00:04:55,930 battery saving but if it does improve 235 00:04:55,930 --> 00:04:58,440 battery saving but if it does improve some of that background performance you 236 00:04:58,440 --> 00:04:58,450 some of that background performance you 237 00:04:58,450 --> 00:04:59,880 some of that background performance you know that could breathe you know a 238 00:04:59,880 --> 00:04:59,890 know that could breathe you know a 239 00:04:59,890 --> 00:05:01,230 know that could breathe you know a little bit of extra life into those 240 00:05:01,230 --> 00:05:01,240 little bit of extra life into those 241 00:05:01,240 --> 00:05:03,390 little bit of extra life into those devices besides I think it's a great 242 00:05:03,390 --> 00:05:03,400 devices besides I think it's a great 243 00:05:03,400 --> 00:05:18,630 devices besides I think it's a great great idea a great feature yeah 244 00:05:18,630 --> 00:05:18,640 245 00:05:18,640 --> 00:05:21,680 [Music]