How to access the GPU report

Reviewing your GPU report

Navigating

The top of the GPU tool offers the ability to navigate between billing cycles. You can use the arrows at the bottom right and left to switch cycles.

NOTE:

The GPU tool will typically only store GPU data for the past 3 billing cycles. Earlier billing cycles may not display.

Viewing details

How do I view data for individual days?

To do this, just click on a data-point on your GPU graph. This will change the data shown in the table below to reflect a single day. You can single out the days with the highest GPU usage to see where your overages are coming from.

What do all these details mean?

You can hover over the title of any column (e.g. "IORead or IOWrite) to see what it means.

Why are some rows yellow?

This means this row has a suggestion. Hover over the yellow triangle (!) to see what the GPU tool thinks about this data.

Why do I have high GPU usage?

Although the number of variables that can cause GPU usage are complex, experience has shown that major GPU drivers are usually caused by site scripting problems or by substantial traffic surges. While the Grid is designed to handle major traffic surges with minimal issue, script-heavy, database-driven websites will almost certainly use more GPUs than simple, static HTML pages.

Tips

Optimizing your scripts can be a difficult task. Here's some general ideas on where to look for help:

If you are using third-party software, look into their documentation or their community forum.

Try disabling plug-ins or add-ons to your site. After a few days, you might see a reduction in GPU usage.

Utilize caching whenever possible. Popular CMS programs like WordPress have caching plugins available. You can also use third-party services like TrueSpeed to cache your page. Caching can lead to immense reductions in usage with very little effort.

If you see high usage from favicon.ico, robot.txt, or other missing system showing a "404" error, this is because most popular CMS software has to do work to generate the 404 on every attempt to reach the missing file. Create a static file for each of these to reduce the resource usage from this error.

TIP:

For further reading on reducing your GPU usage, please see the following article: