Dynatrace

FEBRUARY 4, 2021

As a discipline, SRE focuses on improving software system reliability across key categories including availability, performance, latency, efficiency, capacity, and incident response. ” According to Google, “SRE is what you get when you treat operations as a software problem.”

Engineering 257

Engineering DevOps Government Latency 257

Dynatrace

FEBRUARY 4, 2021

As a discipline, SRE focuses on improving software system reliability across key categories including availability, performance, latency, efficiency, capacity, and incident response. ” According to Google, “SRE is what you get when you treat operations as a software problem.”

Engineering 181

Engineering DevOps Government Latency 181

Dotcom-Montior

OCTOBER 6, 2021

The term site reliability engineering first came into existence at Google in 2003 when a site reliability team was created. that are required to keep the software deployments live are running efficiently. The term “Site Reliability Engineer” is attributed to Ben Treynor Sloss, now a Vice President of Engineering at Google.

Engineering 67

Engineering DevOps Monitoring Google 67

Adrian Cockcroft

JANUARY 20, 2023

Here’s some predictions I’m making: Jack Dongarra’s efforts to highlight the low efficiency of the HPCG benchmark as an issue will influence the next generation of supercomputer architectures to optimize for sparse matrix computations. Jack Dongarra talked about the scores, and pointed out the low efficiency on some important workloads.

Architecture 52

Architecture Latency Benchmarking AWS 52

The Morning Paper

JUNE 23, 2019

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. Yes, a bit like those 2nd-level caches we were talking about earlier, e.g. Ehcache from 2003 onwards. What have the authors got against this combination? Who knew! ;).

Cache 79

Cache Latency Google Lambda 79

Tim Kadlec

JULY 31, 2013

Instead, to support a browser, we want to give the browser what it can handle, in the most efficient way possible. Nick Finck and Steve Champeon first coined the term “progressive enhancement” in 2003. In a comment on my last post I referenced the Boston Globe and how it appears on Google Glass. That was 2008.

Google 40

Google Website Hardware Games 40