Back to blog

Follow and Subscribe

Performance

Page 10 of 11

Cache hit issues? Fix it | Fastly.Rogier Mulhuijzen
The cache hit ratio (or hit ratio for short) is the ratio of hits to cacheable requests (hits and misses combined). There's also cache coverage, the ratio of cacheable requests to all requests (cacheable requests and passes). In most cases, you'll want both to be as high as possible, since misses and passes cause load on your origins, and are slower than cache hits.
PerformanceEngineering
How our solid-state drives result in cost savings for customersSimon Wistow
Solid-State Drives (SSDs) are semiconductor-based storage devices that save persistent data by using NAND flash memory. See how Fastly manages caches with SSDs and how you can save.
PerformanceProduct+1
Boost Cache Efficiency with Origin Log AnalysisRogier Mulhuijzen
If you want to increase the efficiency of your Varnish (or Fastly) cache, you need to figure out what traffic is not cached. By definition, any traffic that reaches your origin is not cached, and thus worthy of investigation.
PerformanceEngineering+1
Accelerating Rails, Part 2: Dynamic HTTP CachingMichael May
In the second part of our series on accelerating Rails, I'll cover configuration of a few Fastly features, Varnish and Varnish Configuration Language (VCL), and strategies for caching dynamic content that are targeted towards the Rails developer.
Performance
Normalizing the Host HeaderRogier Mulhuijzen
In the continued quest to increase cache hit ratios, the chant is: "Normalize, normalize, normalize." Less variation in your requests means you have a higher chance of getting hits. This month's highlight is the Host header.
PerformanceEngineering
Accelerating Rails, Part 1: Built-in CachingMichael May
Caching is one strategy that helps ease scaling pains that I often see Rails developers overlooking. Starting out with caching can be confusing, because terms and documentation can be convoluted, especially if you’re not an expert.
Performance
Using ESI, Part 2: Leveraging VCL and ESI to Use JSONPSimon Wistow
In this post, I’m going to discuss how you can leverage ESI and VCL (Varnish Configuration Language, the domain-specific language that powers Fastly’s edge scripting capabilities) to use JSON responses, even when they’re loaded from another site. This is useful in many cases, including various analytics and social sharing instances.
Performance
Large File Delivery Improved with Streaming Miss Support | FastlySimon Wistow
Today, we’re excited to announce two related features that lower bandwidth costs and reduce origin load for Fastly customers, resulting in faster downloads for their users: Streaming Miss and Large File Support.
StreamingPerformance+1
New Gzip Settings and Deciding What to CompressSteve Souders
Fastly recently conducted an extensive analysis of which resources should be compressed. Today, the results of that analysis are reflected in the Fastly app, which allows our customers to adopt better gzip settings. This not only makes our customers' websites faster, but it will also reduce monthly bandwidth charges.
Performance
Hooman Beheshti talks caching | FastlyHannah Levy
Hooman Beheshti, VP of Technology at Fastly, recently gave a talk at Velocity NYC 2014 about the challenges CDNs face with dynamic content and how businesses can use programmatic means to fully integrate their applications with their CDN.
Performance
Stale-While-Revalidate, Stale-If-Error Available TodaySteve Souders

Fastly is excited to announce that as of today, we support stale-while-revalidate and stale-if-error. As a company dedicated to building a better Internet, we work hard to identify and support new standards that move the Web forward. Read on for an explanation of how these Cache-Control extensions make the Web faster and more reliable for browsers and CDNs, and check out documentation of these features.

PerformanceProduct
Using ESI, Part 1: Simple Edge-Side IncludeSimon Wistow
Fastly customers can use ESI to cache pages that contain both cacheable and uncacheable content (such as user-specific information).
Performance
Best practices for using the Vary headerRogier Mulhuijzen
Vary is one of the most powerful HTTP response headers. However, if used incorrectly, it can cause problems for developers. Understand vary header best practices to reduce mistakes and improve performance.
PerformanceEngineering
Caching “Like” and “Share” ButtonsSimon Wistow

In a blog post about caching with tracking cookies, I explained how Fastly’s edge scripting language allows businesses to cache things that were previously uncacheable as well as send data back via our real-time logging system.

But what happens when you need to cache something more complicated, such as a product that handles user interaction?

Performance
API Caching, Part IIIRyan Richards
In this, our final API Caching installment, we're going to explore how to use Surrogate Keys to reduce the overall complexity of caching an API.
Performance
Building a Fast and Reliable Purging SystemBruce Spang

At Fastly, we’re always working to make our systems faster and more reliable. One of the more difficult problems we’ve faced is efficient cache invalidation across our global network, or as we call it: Instant Purging. When content changes, our customers issue a purge request, which we then need to deliver to each of our cache servers. The system that handles these purge requests is codenamed Powderhorn.

ProductPerformance
How Fastly Chooses POP LocationsChris Hendrie
Why fiber routes, eyeball networks, and growth forecasting, not just population, determine where Fastly places new points of presence on its edge network.
PerformanceProduct+1
API Caching, Part IIRyan Richards

In Part 1, we covered the basics of using Fastly to accelerate a comments API. Using Instant Purge, we hooked into model callbacks to ensure that the appropriate content was purged from the cache whenever data changed. In this article, we’ll build upon the original approach and use one of Fastly’s more advanced features: cache control.

Performance
API Caching, Part IRyan Richards
The web has come a long way since the 90s. In the past, sites were commonly driven by a single, monolithic application that acted as the only communication medium to a centralized database. The modern approach is to break this one large application into a set of interdependent and cooperative services.
Performance
Fastly CDN ExpandsKelly Jandro
At Fastly, we’re constantly working to upgrade our network and expand global capacity. Last week, we built up capacity in our Ashburn, New York City, and Los Angeles POPs and brought a new Miami POP online to improve user experience in South and Central America. We also brought a second London POP online and increased the capacity in our existing London and Frankfurt POPs. In addition to our existing POPs in Tokyo and New Zealand, we’ve added new POPs in Singapore and Hong Kong to bring our customers’ content even closer to users in Asia Pacific. These upgrades are already available to current customers.
PerformanceProduct+2