Opera improving start-up time with experimental flags

[François Beaufort]

Not sure everyone saw this but these flags in Opera Developer 21.0.1432.5 picked my curiosity.

• #delay-onload – This one is my favorite  – after restoring session, onload JS events in background tabs aren’t fired until a tab is activated. It might not sound that important, but during tests this feature was giving the best results – both in loading times, and CPU/memory usage.
• #extended-lazy-session-loading (requires #lazy-session-loading being on) – causes that an active tab + the configured number of tabs (still working on the number, for now it’s 2) is being loaded normally when restoring the session. When any of tabs finishes loading, it triggers the next one to start loading, until all tabs are done. It takes more time to fully restore session, but the start-up itself is much quicker it and takes less CPU.
• #restore-contenteditables-state – the content of elements with contenteditable=”true” is restored on session restoration/history navigation.
• #tab-hibernation – If a background tab is inactive (does not load anything including XHRs, plays any media, plug-in is not streaming any data, or a script is not changing page’s title/favicon) for 40 seconds its process gets suspended and swapped out (causing process memory usage drops significantly). Swapping out happens instantly on Windows and is driven by OS on mac. If the process is shared between couple of tabs, all of them have to be inactive for this to kick in.
• #session-tabs-serialization – all pages from opened tabs are serialized on HDD when closing the browser and are loaded from there instead of the network when restoring the session. This feature should be especially useful for the users with low bandwidth network.
• 
  
• Source: http://blogs.opera.com/desktop/2014/03/opera-developer-21-0-1432-5/
  

[Drew Wilson]

Interesting! I wonder if #delay-onload would break apps that display desktop notifications (i.e. Google Calendar fires up in a tab, but doesn't actually display any notifications for pending events because it's never gotten an onload()). Maybe firing delayed onloads ala #extended-lazy-session-loading would address this.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev