Chromium Blog
News and developments from the open source browser project
Making Chrome on Windows faster with PGO
Montag, 31. Oktober 2016
Chrome is always looking for ways to speed up the web. Starting in Chrome 53, Chrome has started using Microsoft’s
Profile Guided Optimization
(PGO) technology to make Chrome up to 15% faster on Windows.
New tab page load time
14.8% faster
Page load (time to first paint)
5.9% faster
Startup time
16.8% faster
PGO impact on load and startup time
Chrome is a huge software project with more than a million functions in its source code. Not all functions are equal - some are called frequently, while others are rarely used. PGO uses data from runtime execution that track which functions are most common to guide optimization.
To gather this data, the nightly build process now produces a special version of Chrome that tracks how often functions are used. PGO then optimizes those high-use functions for speed, in some cases increasing the binary size of those functions. To balance out that increase, PGO also optimizes less-used functions with smaller, though slightly slower code. These trade-offs result in higher overall performance, and a smaller overall code footprint.
PGO also optimizes the memory location of the code, moving rarely-used functions away from frequently-used ones in memory. This results in more optimal use of the CPU instruction cache by avoiding caching of less-used code, increasing overall performance. There are
many other tricks
that PGO uses to make Chrome faster, and they add up to great results.
64-bit Chrome on Windows is using PGO as of version 53, and 32-bit Chrome is using it as of version 54. Try out the latest version of Chrome to see the difference with PGO.
Posted by Sébastien Marchand, who is Pretty Good at Optimizing.
Chrome 55 Beta: Input handling improvements and async/await functions
Freitag, 21. Oktober 2016
Unless otherwise noted, changes described below apply to the newest Chrome
Beta
channel release for Android, Chrome OS, Linux, Mac, and Windows.
Input handling improvements
As usage of the mobile web grows, it is increasingly important for sites to react well to touch input. Historically, this meant handling
MouseEvent
and
TouchEvent
separately, which can be difficult to maintain. Chrome now
enables unified input handling
by dispatching
PointerEvents
.
PointerEvents
lead to more responsive pages, as they don’t block scrolling by default. To achieve the same performance with
TouchEvent
, pages can use
passive event listeners
.
Chrome also now supports two new ways to respond to input. The
touch-action
CSS property
enables sites to react to gestures such as panning. For mouse buttons, the new
auxclick
input event type
allows sites to manage the click behavior of non-primary buttons.
Async and await functions
Asynchronous JavaScript can be difficult to reason about. Promises help avoid the nesting problem of callbacks, but Promise-based code can still be difficult to read when a site has large chains of asynchronous dependencies. Chrome now supports the
async
and
await
JavaScript keywords, allowing developers to write Promise-based JavaScript that can be as structured and readable as synchronous code.
Fetching a URL and logging the response using Promises:
function
logFetch(url) {
return
fetch(url)
.
then
(response => response.text())
.
then
(text => {
console.log(text);
}).
catch
(err => {
console.error(
'fetch failed'
, err);
});
}
The same code using async and await:
async
function
logFetch(url) {
try
{
const
response = await fetch(url);
console.log(await response.text());
}
catch
(err) {
console.log(
'fetch failed'
, err);
}
}
CSS automatic hyphenation
Formatting text to fill available space can be a challenge across devices and screen sizes. Chrome now supports
CSS automatic hyphenation
, one of Chrome’s most frequently requested layout features, on Android and Mac. CSS hyphenation allows the browser to hyphenate words when line-wrapping, improving the visual consistency of text blocks. Hyphenation support will be extended to other platforms in future releases.
A paragraph rendered with and without automatic hyphenation
Other features in this release
The
once
event listener option
enables callbacks to be invoked only once before removing the event listener.
Sites can now mark web storage as
persistent
, preventing Chrome from automatically clearing storage for that site.
Cross-origin iframes now require a user gesture to start audio playback using the
Web Audio API
o
n Android, matching the behavior of the
<audio>
and
<video>
elements
.
The TLS stack now implements
GREASE
, a mechanism to help prevent problems with buggy TLS servers.
Developers can create a
MediaStreamTrackEvent
in an alternative way with its new JavaScript constructor.
RSA-PSS signature algorithms have been added to TLS to prepare for
TLS 1.3
.
To
improve load times and prevent failed navigations
,
cross-origin and parser-blocking scripts injected using
document.write()
will no longer load over 2G connections
.
AudioNode
constructors of the form
new AudioNode(context, options)
are now available, making it simpler to manage audio from scripts.
When the media player is too narrow to show every button, an
overflow menu
will appear to provide the hidden functionality to users.
Chrome media controls will now
display a download button
when the playback is associated with a file that can be downloaded.
The
Web Share API
is available for
experimentation
as an
origin trial
.
Deprecations and interoperability improvements
BaseAudioContext
will replace
AudioContext
in the
Web Audio API
to conform to spec.
CSS Clipping Path properties no longer require the
webkit
prefix.
The
MediaStream
constructor is now available without prefix alongside the existing
webkitMediaStream
.
Non-script
MIME types
will no longer trigger script execution.
<textarea maxlength="">
and
<textarea minlength="">
have been updated to count each line break as one character, instead of two.
The
webkit
prefix has been removed from the
imageSmoothingEnabled
property of
CanvasRenderingContext2D
.
Posted by Dan Ehrenberg, Asynchronous Adventurer
Canary channel for Chrome on Android
Dienstag, 18. Oktober 2016
Chrome supports multiple
release channels
with varying degrees of stability and support. The Canary channel ships the most bleeding edge version of Chrome possible. It is primarily intended to be used by developers and early adopters to test recent Chromium changes, but anyone can install it and give it a try. Previously the Canary channel was only available on Windows and Mac, and it is now
available for Android
as well.
Just like the Canary channel for other platforms, new versions are built from the most recent code available and often contain a variety of new features, enhancements, and bug fixes. These builds are shipped automatically with no manual testing, which means that the build can be unstable and may even stop working entirely for days at a time. However, the goal is for Canary to remain usable at all times, and the Chrome team prioritizes fixing major issues as quickly as possible.
Initially, builds will ship every weekday. In the future new builds may also be available on weekends. The frequency of builds means that keeping the app updated will consume a lot of data, typically more than 100MB per week. This is especially important for phones set to update native apps over cellular data.
We hope the Canary channel will be useful when developing and testing changes for Chrome on Android. If you encounter any bugs, please help us by
reporting them
.
Posted by Alex Mineer, APK Administrator & Bug Basher
Labels
$200K
1
10th birthday
4
abusive ads
1
abusive notifications
2
accessibility
3
ad blockers
1
ad blocking
2
advanced capabilities
1
android
2
anti abuse
1
anti-deception
1
background periodic sync
1
badging
1
benchmarks
1
beta
83
better ads standards
1
billing
1
birthday
4
blink
2
browser
2
browser interoperability
1
bundles
1
capabilities
6
capable web
1
cds
1
cds18
2
cds2018
1
chrome
35
chrome 81
1
chrome 83
2
chrome 84
2
chrome ads
1
chrome apps
5
Chrome dev
1
chrome dev summit
1
chrome dev summit 2018
1
chrome dev summit 2019
1
chrome developer
1
Chrome Developer Center
1
chrome developer summit
1
chrome devtools
1
Chrome extension
1
chrome extensions
3
Chrome Frame
1
Chrome lite
1
Chrome on Android
2
chrome on ios
1
Chrome on Mac
1
Chrome OS
1
chrome privacy
4
chrome releases
1
chrome security
10
chrome web store
32
chromedevtools
1
chromeframe
3
chromeos
4
chromeos.dev
1
chromium
9
cloud print
1
coalition
1
coalition for better ads
1
contact picker
1
content indexing
1
cookies
1
core web vitals
2
csrf
1
css
1
cumulative layout shift
1
custom tabs
1
dart
8
dashboard
1
Data Saver
3
Data saver desktop extension
1
day 2
1
deceptive installation
1
declarative net request api
1
design
2
developer dashboard
1
Developer Program Policy
2
developer website
1
devtools
13
digital event
1
discoverability
1
DNS-over-HTTPS
4
DoH
4
emoji
1
emscriptem
1
enterprise
1
extensions
27
Fast badging
1
faster web
1
features
1
feedback
2
field data
1
first input delay
1
Follow
1
fonts
1
form controls
1
frameworks
1
fugu
2
fund
1
funding
1
gdd
1
google earth
1
google event
1
google io 2019
1
google web developer
1
googlechrome
12
harmful ads
1
html5
11
HTTP/3
1
HTTPS
4
iframes
1
images
1
incognito
1
insecure forms
1
intent to explain
1
ios
1
ios Chrome
1
issue tracker
3
jank
1
javascript
5
lab data
1
labelling
1
largest contentful paint
1
launch
1
lazy-loading
1
lighthouse
2
linux
2
Lite Mode
2
Lite pages
1
loading interventions
1
loading optimizations
1
lock icon
1
long-tail
1
mac
1
manifest v3
2
metrics
2
microsoft edge
1
mixed forms
1
mobile
2
na
1
native client
8
native file system
1
New Features
5
notifications
1
octane
1
open web
4
origin trials
2
pagespeed insights
1
pagespeedinsights
1
passwords
1
payment handler
1
payment request
1
payments
2
performance
20
performance tools
1
permission UI
1
permissions
1
play store
1
portals
3
prefetching
1
privacy
2
privacy sandbox
4
private prefetch proxy
1
profile guided optimization
1
progressive web apps
2
Project Strobe
1
protection
1
pwa
1
QUIC
1
quieter permissions
1
releases
3
removals
1
rlz
1
root program
1
safe browsing
2
Secure DNS
2
security
36
site isolation
1
slow loading
1
sms receiver
1
spam policy
1
spdy
2
spectre
1
speed
4
ssl
2
store listing
1
strobe
2
subscription pages
1
suspicious site reporter extension
1
TCP
1
the fast and the curious
23
TLS
1
tools
1
tracing
1
transparency
1
trusted web activities
1
twa
2
user agent string
1
user data policy
1
v8
6
video
2
wasm
1
web
1
web apps
1
web assembly
2
web developers
1
web intents
1
web packaging
1
web payments
1
web platform
1
web request api
1
web vitals
1
web.dev
1
web.dev live
1
webapi
1
webassembly
1
webaudio
3
webgl
7
webkit
5
WebM
1
webmaster
1
webp
5
webrtc
6
websockets
5
webtiming
1
writable-files
1
yerba beuna center for the arts
1
Archive
2024
Aug.
Juni
Mai
Apr.
März
Feb.
2023
Nov.
Okt.
Sept.
Aug.
Juni
Mai
Apr.
Feb.
2022
Dez.
Sept.
Aug.
Juni
Mai
Apr.
März
Feb.
Jan.
2021
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2020
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2019
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2018
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2017
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2016
Dez.
Nov.
Okt.
Sept.
Aug.
Juni
Mai
Apr.
März
Feb.
Jan.
2015
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2014
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2013
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2012
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2011
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2010
Dez.
Nov.
Okt.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2009
Dez.
Nov.
Sept.
Aug.
Juli
Juni
Mai
Apr.
März
Feb.
Jan.
2008
Dez.
Nov.
Okt.
Sept.
Feed
Follow @ChromiumDev
Give us feedback in our
Product Forums
.