Remove 2003 Remove Google Remove Performance Remove Scalability
article thumbnail

Site reliability engineering: 5 things you need to know

Dynatrace

Site reliability engineering (SRE) is the practice of applying software engineering principles to operations and infrastructure processes to help organizations create highly reliable and scalable software systems. ” According to Google, “SRE is what you get when you treat operations as a software problem.”

article thumbnail

Site reliability engineering: 5 things to you need to know

Dynatrace

Site reliability engineering (SRE) is the practice of applying software engineering principles to operations and infrastructure processes to help organizations create highly reliable and scalable software systems. ” According to Google, “SRE is what you get when you treat operations as a software problem.”

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

What is a Site Reliability Engineer (SRE)?

Dotcom-Montior

The term site reliability engineering first came into existence at Google in 2003 when a site reliability team was created. Performance. The term “Site Reliability Engineer” is attributed to Ben Treynor Sloss, now a Vice President of Engineering at Google. At that time, the team was made up of software engineers.

article thumbnail

Supercomputing Predictions: Custom CPUs, CXL3.0, and Petalith Architectures

Adrian Cockcroft

on Myths and Legends of High Performance Computing  — it’s a somewhat light-hearted look at some of the same issues by the leader of the team that built the Fugaku system I mention below. The emergence of chiplet technology also allows higher performance and integration without having to design every chip from scratch.

article thumbnail

Fast key-value stores: an idea whose time has come and gone

The Morning Paper

I say go ahead and use local state as a performance boost, so long as you’re fine to have that state wiped out at any moment. In ProtoCache (a component of a widely used Google application), 27% of its latency when using a traditional S+RInK design came from marshalling/un-marshalling. Who knew! ;). From RInK to LInK.

Cache 79
article thumbnail

WebPageTest API

CSS - Tricks

It is the premier tool in the toolbox of web performance people. Here’s the real news though: there’s a full-on scalable API now. google-analytics.com", "sanList":[ "*.google-analytics.com", google-analytics.com", "*.fps.goog", I’m willing to bet you know WebPageTest. Linux; Android 6.0.1;

article thumbnail

What Adrian Did Next?—?Part 2?—?Sun Microsystems

Adrian Cockcroft

I became the Sun UK local specialist in performance and hardware, and as Sun transitioned from a desktop workstation company to sell high end multiprocessor servers I was helping customers find and fix scalability problems. Rich became co-author of the second edition of the Sun Performance Tuning book, to describe how it worked.

Tuning 52