Don Thorp's Library tagged performance →  View Popular, Search in Google

vps performance

javascript performance

google CDN performance web

On April 7th, Google launched a new version of Gmail for mobile for iPhone and Android-powered devices. We shared the behind-the-scenes story through this blog and decided to share more of what we've learned in a brief series of follow-up blog posts. This week, I'll talk about how modularization can be used to greatly reduce the startup latency of a web app.

To a user, the startup latency of an HTML 5 based application is critical. It is their first impression of the application's performance. If it's really slow, they might not even bother to wait for the app to load before navigating away. Even if your application is blazing fast after it loads, the user may never get the chance to experience it.

performance javascript html5

The new Android 1.5 Early Look SDK is out since a few weeks. The "Android 1.5 highlights" page does not mention one highlight, which IMHO will become very important for all developers on the Android platform because it allows you to find memory leaks easily and analyze the memory usage of your Android applications.

I'm talking about the hprof-conv tool that allows you to convert an Android/Dalvik heap dump into an .hprof heap dump. The tool does not preserve all the information, because Dalvik has some unique features such as cross-process data sharing, that are not available in a "standard" JVM. Still the .hprof file is a good starting point and can be read with the Eclipse Memory Analyzer, which will interpret it like a normal file from a Sun 32 bit JVM. In the future it should also be not that difficult to read the Dalvik heap dump format directly and provide more information for memory analysis, such as which objects are shared and also maybe how much memory is used by native Objects (haven't checked that).

android java performance

This post is based on a chapter from Even Faster Web Sites, the follow-up to High Performance Web Sites. Posts in this series include: chapters and contributing authors, Splitting the Initial Payload, Loading Scripts Without Blocking, Coupling Asynchronous Scripts, Positioning Inline Scripts, Sharding Dominant Domains, Flushing the Document Early, Using Iframes Sparingly, and Simplifying CSS Selectors.

“Simplifying CSS Selectors” is the last chapter in my next book. My investigation into CSS selector performance is therefore fairly recent. A few months ago, I wrote a blog post about the Performance Impact of CSS Selectors. It talks about the different types of CSS selectors, which ones are hypothesized to be the most painful, and how the impact of selector matching might be overestimated. It concludes with this hypothesis:

css performance

Are your web apps slow?Bug

Is there anything more annoying than a slow web application?

Great interfaces are nice. Pretty graphics are, too. Functionality is great. But if a web app doesn't perform fast enough, it'll end up going down the intertubes.

So, is your app slow? Do you know for sure? Do you know how to find out? And if you do find problems, do you know how to fix them, what to target first, and what not to do in your quest for better performance?

Even if you don't experience performance problems (yet),
you can almost surely speed things up.

ebook javascript performance

Recently while testing an Android mobile application our team was developing, we encountered some performance issues in two of our List Views. Fortunately, the Android SDK provides mature debugging tools to help investigate performance problems. In this post, I'll describe how we used Android's toolset to locate the source of our problems and verify the optimizations we made were correct. I'll also share a few tips to keep in mind while tracing your own Android applications.

android performance