Tuesday, January 30, 2018

Take advantage of the JavaScript compilation cache (Chromium)

our company maintains a GWT application where the development was started 4 years ago and where several dozens of developers has worked on it.

The current version of GWT used is 2.5.1 and the application will be accessible only through the Chromium browser embedded in an ad-hoc client built by using Electron.

Altough we use the GWT code splitting feature, our application suffers of a performance issue because the GWT initial load is 29MB and the user login process spends most time to parse/compile the GWT initial load.

We noted that the V8 JavaScript engine used by Chromium supports a JavaScript code caching mechanism in order to mitigate that kinds of performance issue that we suffer.

So is it possible for a GWT application to take advantage of the V8 JavaScript code cache?

From our tests, we noted that the GWT initial load (embedded in thousands of <script> tags of the XXXXXXXX.cache.html file) is always compiled, even after login/logout operation executed sequentially without closing the browser.


You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment