Rails in the Large: How Agility Allows Us to Build One Of the World's Biggest Rails Apps
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Jun 05, 2009
Google has just open sourced Page Speed, a tool used internally by Google to optimize their web sites, especially the speed web pages are loaded with.
Page Speed is a Firefox add-on running in Firebug. The tool runs on Linux, Mac and Windows XP/Vista. When it runs, Page Speed analyzes some of the web server’s configuration plus the code downloaded from the server and creates a list of results including suggestions on how to improve the web pages. The analysis is based on a list of best practices organized in five categories:
- Optimizing caching — keeping your application's data and logic off the network altogether
- Minimizing round-trip times — reducing the number of serial request-response cycles
- Minimizing request size — reducing upload size
- Minimizing payload size — reducing the size of responses, downloads, and cached pages
- Optimizing browser rendering — improving the browser's layout of a page
These practices consider the page load time, the time between a page request is issued and the moment it is served as seen by the client. The page load time includes creating TCP connections, solving DNS names, sending requests, fetching resources including those from cache, executing scripts, rendering.
The suggestions offered by the tool are:
The suggestions are scored and sorted by priority. An example, when loading Facebook’s home page, the following high priority suggestion is given: “The following external CSS files were included after an external JavaScript file in the document head. To ensure CSS files are downloaded in parallel, always include external CSS before external JavaScript.”
The Page Speed Activity panel shows all browser’s activity including network events and JavaScript code execution measured in ms. This is useful to see where the browser spends most of the time when trying to load a certain page. Overall, Page Speed seems like a must-have tool for web developers.
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
Technical Debt and Design Death
Agile Development e-Kit: Educational Content from Rational
Lean development governance whitepaper by Scott Ambler and Per Kroll
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Stuart Halloway discusses Clojure and functional programing on the JVM in depth, and touches on the uses of a number of other modern JVM languages including JRuby, Groovy, Scala and Haskell.
Orion Henry and Blake Mizerany talk about the technology behind Heroku and the benefits of the new add-on system.
Chris Riley presents security issues threatening service based systems, examining security threats, presenting measures to reduce the risks, and mentioning available security frameworks.
This talk investigates technical issues encountered when moving to an Agile process.
Don Box and Amanda Laucher present “M”, a declarative language for building data models, domain models or external DSLs. Don Box's demos show some of M’s features and latest changes of the language.
It is four months since the SOA manifesto was announced; InfoQ interviewed the original author’s to get insight into the motivations and the process behind the initiative.
This article explains the impact memory barriers, or fences, have on the determinism of multi-threaded programs.
3 comments
Watch Thread Reply