Google News

Posted by Jason Shafton, Inside AdWords crew

This is a guest post by Owen Barton, partner and director of engineering at CivicActions. Owen has been working with Google's “Make the Web Faster” project team and the Drupal community to make improvements in Drupal 7 front-end performance. This is a condensed version of a more in-depth post over at the CivicActions blog.

Drupal is a popular free and open source publishing platform, powering high profile sites such as The White House, The New York Observer and Amnesty International. The Drupal community has long understood the importance of good front-end performance to successful web sites, being ahead of the game in many ways. This post highlights some of the improvements developed for the upcoming Drupal 7 release, several of which can save an additional second or more of page load times.

Drupal 7 has made its caching system more easily pluggable - to allow for easier memcache integration, for example. It has also enabled caching HTTP headers to be set so that logged out users can cache entire pages locally as well as improve compatibility with reverse proxies and content distribution networks (CDNs). There is also a patch waiting which reduces both the response size and the time taken to generate 404 responses for inlined page assets. Depending on the type of 404 (CSS have a larger effect than images, for example) the slower 404s were adding 0.5 to 1 second to the calling page load times.

Drupal currently has the ability to aggregate multiple CSS and JavaScript files by concatenating them into a smaller number of files to reduce the number of HTTP requests. There is a patch in the queue for Drupal 7 that could allow aggregation to be enabled by default, which is great because the large number of individual files can add anything from 0-1.5 seconds to page loads.

One issue that has become apparent with the Drupal 6 aggregation system is that users can end up downloading aggregate files that include a large amount of duplicate code. On one page the aggregate may contain files a, b and c, whilst on a second page the aggregate may contain files a, b and d - the “c” and “d” files being added conditionally on specific pages. This breaks the benefits of browser caching and slows down subsequent page loads. Benchmarking on core alone shows that avoiding duplicate aggregates can save over a second across 5 page loads. A patch has already been committed that means files need to be explicitly added to the aggregate, and fix Drupal core to add appropriate files to the aggregate unconditionally.

Drupal has supported gzip compression of HTML output for a long time, however for CSS and JavaScript, the files are delivered directly by the webserver, so Drupal has less control. There are webserver based compressors such as Apache’s mod_deflate, but these are not always available. A patch is in the queue that stores compressed versions of aggregated files on write and uses rewrite and header directives in .htaccess that allow these files to be served correctly. Benchmarks show that this patch can make initial page views 20-60% faster, saving anything from 0.3 to 3 seconds total.

The Drupal 7 release promises some real improvements from a front-end performance point of view. Other performance optimizations will no doubt continue to appear and be refined in contributed modules and themes, as well as in site building best practices and documentation. In Drupal 8 we will hopefully see further improvements in the CSS/JS file aggregation system, increased high-level caching effectiveness and hopefully more tools to help site builders reduce file sizes. If you have yet to try Drupal, download it now and give it a try and tell us in the comments if your site performance improves!

By Owen Barton of CivicActions

Back in June, we announced the Conversion Champion Challenge, a contest to help motivate you to get your conversion rates in shape for summer. Many of you embraced the challenge - with increased profits to show for it! However, one advertiser stood out among the rest as the true Conversion Champion. We’re delighted to invite Elliott Antal from Richard Petty Driving Experience, to the Google Headquarters in Mountain View, CA, to spend a day with the Google Conversion team. Elliott told us a bit about his journey to the finish line:

“The Conversion Champion Challenge was the perfect opportunity [for Richard Petty Driving Experience] to try some new tools in regards to our paid search marketing.

Richard Petty Driving Experience is the world's largest provider of NASCAR ride and drive entertainment and the exclusive stock car experience at premiere tracks such as Daytona International Speedway, Las Vegas Motor Speedway, and Walt Disney World Speedway. A conversion for Richard Petty Driving Experience is a completed e-commerce transaction. Customers have the opportunity to purchase a ride, drive, or merchandise through www.DrivePetty.com.

On June 11, we activated the Conversion Optimizer for our primary search campaign. In the time after the activation we have seen our conversion rate increase by 10% and cost-per-acquisition drop 2%. We’ve also seen our clicks double, with average cost-per-click decreasing by 30%. Conversions are coming in at a healthy pace while maximizing the reach of our budget. Conversion Optimizer has most certainly made a positive impact on our account and performance is continuing to improve over time.”

Well done, Elliott! We look forward to meeting you in person and exploring more ways to boost your ROI.

To learn more the Conversion Optimizer, an automatic bidding tool for increasing your ROI, visit the Conversion Optimizer site.

click for full size image

Posted by Miles Johnson, Inside AdWords crew

We are now ready to share the Google Developer Day agendas for Tokyo, Sao Paulo, Munich, Moscow and Prague. We have so much technical content to share but alas, Developer Day is a one-day event. There may still be changes to the agenda, but here is a sneak peek at where we are.

Globally, we will feature three major tracks:

• Android - With the continued momentum and growth of the platform, we would like to continue the conversation with you at Developer Day. We will feature sessions on Android performance, mobile user experience and best practices on building apps, and we will also deep dive on a new feature, Cloud to Device Messaging (C2DM).


• Chrome & HTML5 - We will discuss how to build an app for the Chrome Web Store and how to improve its development and performance. We’ll show which aspects of HTML5, Chrome Developer Tools and Native Client can be most useful to you. Finally, we will cover everything auth-related to show you when and where to use various authentication tools and how they integrate with our APIs and products.


• Cloud Platform - Building off of our series of announcements at Google I/O, we will feature sessions on App Engine, App Engine for Business, Spring integration, Google Web Toolkit, Google Storage for Developers, BigQuery and Prediction API. Be prepared for code samples, how to optimize performance and a glimpse into what else is on our roadmap.

We are happy to announce that Eric Tholome, Product Management Director for Developer Products, will be a keynote speaker in Sao Paulo, Munich, Moscow and Prague. In addition, we are happy to invite as our second keynote speaker:

• Sao Paulo, Brazil - Mario Queiroz, VP Product Management


• Munich, Germany - Dr. Wieland Holfelder, Engineering Director


• Moscow, Russia - Dr. Gene Sokolov, Head of Moscow Engineering

Due to the success of the Venture Capital sessions at Google I/O and the growing VC activity in our global markets, a new addition this year is Venture Capital panels at most of our Developer Days. Come hear from your local VCs on what they look for in startups.

The Sao Paulo and Moscow keynote presentations will have live translation, and for sessions, check the FAQ section of your Developer Day site. We will have savvy gurus available to answer your questions during Office Hours, and you will have a chance to meet Googlers and each other over Happy Hour.

Registration will open on September 15th for Sao Paulo and on September 22nd for Munich, Moscow and Prague. Tokyo’s registration is now closed.

Just a heads up that it should now be easier for users to find SVG files when searching on Google. That’s right, we’ve expanded our indexing capabilities to include SVG. Feel free to check out our Webmaster Help Center for the complete list of file types we support, and our Webmaster Blog for more information on our SVG announcement.

By Maile Ohye, Google Developer Relations

Members of the AdSense team from all over the world say hello from Mountain View, CA!



Posted by Katrina Kurnit - Inside AdSense Team

(Cross-posted from the Google Chrome Blog)

Watching the 1985 classic Back to the Future last night, I was struck by how much things can change with time. The main character Marty McFly travels 30 years back in time, only to find that his house hadn’t been built yet, skateboards hadn’t been invented and nobody had ever heard rock ‘n roll.

Looking back today on Chrome’s second anniversary, it’s amazing to see how much has changed in just a short time. In August 2008, JavaScript was 10 times slower, HTML5 support wasn’t yet an essential feature in modern browsers, and the idea of a sandboxed, multi-process browser was only a research project. All browsers have come a long way in the last two years and the web has become much more fun and useful.


Since Chrome’s first beta launch for Windows, we’ve brought our Mac and Linux versions up to speed, and continued to make the browser faster, simpler, and safer across all three platforms. We’ve also introduced a boatload of features, including a more customizable New Tab page, browser themes, side-by-side view, password manager, better privacy controls, built-in Adobe Flash Player, Autofill, automatic translation, HTML5 capabilities and synchronization of various settings such as bookmarks, themes, extensions and browser preferences—just to name a few. Finally, there are now more than 6,000 extensions in our gallery to enhance your browsing experience.

Behind the scenes, we continue to extend the security features that help you browse the web more safely. This includes Chrome’s Safe Browsing technology—which serves as a warning system if you’re about to visit a site suspected of phishing or hosting malware; Chrome’s auto-update mechanism—which helps ensure that the browser is always up-to-date with the latest security updates; and the browser’s “sandbox”—an added layer of protection which prevents malicious code on an exploited website from infecting your computer.




Today, we’re releasing a new stable version of Chrome that is even faster and more streamlined. Chrome is now three times faster than it was two years ago on JavaScript performance. We’ve also been working on simplifying the “chrome” of Chrome. As you can see, we took the already minimalist user interface and stripped it down a bit more to make it easier to use. We combined Chrome’s two menus into one, revisited the location of the buttons, cleaned up the treatment of the URL and the Omnibox, and adjusted the color scheme of the browser to be easier on the eyes.

Sliding back into Doc Brown’s DeLorean and setting the dial ahead by a few months, we have more in store for Chrome. As always, we’re hard at work on making Chrome even faster, and working on ways to improve graphics performance in the browser through hardware acceleration. With the Chrome Web Store, we hope to make it much easier to find and use great applications on the web. We also ratcheted up the pace of our releases so that we can get new features and improvements to everyone more quickly.

If you haven’t tried Chrome recently, we invite you to download our new stable version today at google.com/chrome. For those of you who have been using Chrome, thanks for a great second year! We hope that Chrome has made your life on the web even better, and look forward to the next year.


Posted by Brian Rakowski, Product Manager

Editor's note: Continuing our “Going Google Everywhere” series, we’ve invited Mark Burgess, IT Director of The Richmond Group - a UK based finance company with 350 employees and the recipient of numerous awards for growth, innovation and employee workplace. They migrated to Google Apps in January 2010 with the support of Insight, a leading global single source provider of IT products and services. Learn more about other organizations that have gone Google on our community map.

When I look back at the decision we made 12 months ago to migrate away from Microsoft Outlook and Microsoft Exchange, it was primarily to solve some of the common problems that come with rapid business expansion – our business has grown at over 50% each year for the past seven years. Reaching mailbox quotas were a way of life, disk capacity limits had been exceeded more than once, we had servers to patch, maintain and backup and it was all distracting us from doing what we do well – creating innovative and unique financial products for our customers.

In January 2010 The Richmond Group went Google. With support from our account manager Brinder Bhamra and the rest of the Google Apps team at Insight, a Google Apps Authorized Reseller, we migrated 350 users away from Microsoft Outlook and into the cloud with Google Apps. While I wish some of the Microsoft Exchange migration tools existed then that are available now, the migration went well and it didn’t take long for users to embrace the new system available to them.

During the migration we concentrated specifically on email, calendar and contacts. With users spread across several sites, Google Talk soon became invaluable, improving real-time communication and helping to speed up decision-making. Being able to access our email from any web connected PC, easily search and find our emails, and benefit from threaded conversations has made managing our emails a whole lot easier!

It’s quite exciting to see the product evolve week by week, rather than every three years which is what we were used to from our previous email solution. Highlights for me have been the rich collaboration that is now possible in Google Docs, contextual gadgets in Gmail and more recently the Google Apps Marketplace. It has really got me thinking about how we can integrate with Google Apps and launch our own applications in the Marketplace. Then, in addition to saving money on our email and collaboration systems, we could build new revenue streams as well!



Posted by Laura Quinn, Google Apps team

One weekday evening a few weeks before our son was born, my wife commissioned me to find a box of raspberry red leaf tea for the delivery. I promptly drove to the nearest grocery store, which has an awe-inspiring wall of tea. After diligently scanning the wall and not finding the tea, I began to wonder if it even existed. Was the similarly-labeled raspberry tea the same thing? What about red leaf tea? Stumped, I pulled out my phone and looked up "raspberry red leaf tea" on Google. Beneath the "Shopping results," I saw a red map marker for a nearby Vitamin Shoppe and a link, "In stock nearby," next to a picture of Alvita Raspberry Red Leaf Tea. I hopped back in the car, and 15 minutes later had accomplished my mission. Two weeks later, my wife accomplished her much more important mission and we welcomed Benjamin, a healthy and happy baby boy, to our family.


Since we announced the Local Shopping inventory beta some months ago, we have received great user feedback on the feature, and retailers have been clamoring to take part. Today, we’re making public our help documentation for participation. Please take a moment to review those documents, and if you’re interested, fill out the local shopping interest form. While we won’t be able to accept all retailers who apply, we will keep your name on file if we can’t take you at this time. Please note that excellent Product Search data quality is a prerequisite for participation, so make sure that you are submitting an accurate and complete data feed, including unique product identifiers. Additionally, to take part you’ll need to have your stores listed on Google Places, so make sure you have submitted and verified your store listings.

Posted by Paul Lee, Business Product Manager, Google Product Search

Posted by Dennis Abts, Michael R. Marty, Philip M. Wells, Peter Klausler, and Hong Liu

This is part of the series highlighting some notable publications by Googlers.

At Google, we operate large datacenters containing clusters of servers, networking switches, and more. While this gear costs a lot of money, an increasingly important cost -- both in terms of dollars and environmental impact -- is the electricity that drives the computing clusters and the cooling infrastructure. Since our clusters often do not run at full utilization, Google recently put forth a call to industry and researchers to develop energy proportional computer systems. With such systems, the power consumed by our clusters would be directly proportional to utilization. Servers consume the most electricity, and therefore researchers have responded to Google’s call by focusing their attention towards servers. As the servers become increasingly energy proportional, however, the “always on” network fabric that connects servers together will consume an increasing fraction of datacenter power unless it too becomes energy proportional.

In a paper recently published at the International Symposium on Computer Architecture (ISCA), we push further towards the goal of energy-proportional computing by focusing on the energy usage of high-bandwidth, highly-scalable cluster networking fabrics. This research considers a broad set of architectural and technological solutions to optimize energy usage without sacrificing performance. First, we show how the Flattened Butterfly network topology uses less power since it uses less switching chips and fewer links than a comparable-performance network built using the more conventional Fat Tree topology. Second, our approach takes advantage of the observation that when network demand is low, we can reduce the speed at which links transmit data. We show via simulation, that by tuning the speeds of the links very rapidly, we can reduce power consumption with little impact on performance. Finally, our research is a further call to action for the academic and industry research communities to make energy efficiency, and energy proportionality in particular, a first-class citizen in networking research. Put together, our proposed techniques can reduce energy cost for typical Google workloads seen in our production datacenters by millions of dollars!