Configuring Warmup Requests to Improve Performance

This guide describes how to configure your app to handle warmup requests. With warmup requests enabled, the App Engine infrastructure issues GET requests to /_ah/warmup. You can implement handlers for this request to perform application-specific tasks, such as pre-caching application data.

Enabling warmup requests

In Go, warmup requests are disabled by default. To enable them, add - warmup to the inbound_services directive in app.yaml:

- warmup

Registering your handler

To register your handler, define the script to handle your warmup requests in your app.yaml file. For example:

- warmup

- url: /_ah/warmup
  script: _go_app
  login: admin

This example registers a handler to listen to warmup requests to the /_ah/warmup request path with the script handler in the app.go file.

Creating your handler

Build any logic that you need to run into a handler that you map to respond to the /_ah/warmup request path. The following example builds on the previous example:

package warmup

import (


func init() {
	http.HandleFunc("/_ah/warmup", warmupHandler)

func warmupHandler(w http.ResponseWriter, r *http.Request) {
	ctx := appengine.NewContext(r)

	// Perform warmup tasks, including ones that require a context,
	// such as retrieving data from Datastore.

	log.Infof(ctx, "warmup done")

What's next

The examples above provide a framework to work within. Next, you'll want to decide what logic belongs in your warmup request handlers. You might want to add values into memcache that your application will need. For example, if you build and store a list of the current trending articles for your site, building that list in the warmup and then storing the necessary data in memcache means that when a user request comes in, the application has everything ready to serve and no queries are performed on the user's request for that data, which results in a faster response.

Related topics:

Send feedback about...

App Engine standard environment for Go