Remove 2015 Remove Benchmarking Remove Blog Remove Cache
article thumbnail

The Return of the Frame Pointers

Brendan Gregg

Only in extreme circumstances does the cost (in processor time and I-cache footprint) translate to a tangible benefit - circumstances which usually resort to hand-coded assembly anyway. It shouldn't be 10%, unless it's cache effects. And for leaf routines (which never establish a frame), this is a non-issue.

Java 145
article thumbnail

How I Used Brotli to Get Even Smaller CSS and JavaScript Files at CDN Scale

CSS - Tricks

In 2015, Google published a blog post announcing Brotli and released its source code on GitHub. The service categorized all the optimizations in three groups consisting of several “Content,” “Delivery,” and “Cache” optimizations. We only cache hot files in memory at edge servers. Brotli’s beginning…. This is all so good.

Cache 79
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Is Intel Doomed in the Server CPU Space?

SQL Performance

The Tick-Tock release cycle basically fell apart by about 2015 , as Intel was unable to move from a 14nm manufacturing process to a 10nm manufacturing process. I wrote a number of blog posts about this back in January 2018, including these: Checking Your SQL Server Instance for Spectre/Meltdown Patches.

Servers 46
article thumbnail

Front-End Performance Checklist 2021

Smashing Magazine

Build Optimizations JavaScript modules, module/nomodule pattern, tree-shaking, code-splitting, scope-hoisting, Webpack, differential serving, web worker, WebAssembly, JavaScript bundles, React, SPA, partial hydration, import on interaction, 3rd-parties, cache. compared to early 2015. Shipped in Next.js and in Gatsby v2.20.7.