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. SRE applies DevOps principles to developing systems and software that help increase site reliability and performance.

Engineering 252

Engineering DevOps Government Latency 252

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. SRE applies DevOps principles to developing systems and software that help increase site reliability and performance.

Engineering 173

Engineering DevOps Government Latency 173

Adrian Cockcroft

JANUARY 20, 2023

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.

Architecture 52

Architecture Latency Benchmarking AWS 52

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. Performance. He was asked in 2003 to create and manage a team of seven engineers which eventually led him to create the new role/title. appeared first on Dotcom-Monitor Web Performance Blog.

Engineering 67

Engineering DevOps Monitoring Google 67

The Morning Paper

JUNE 23, 2019

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. Fetching too much data in a single query (i.e.,

Cache 79

Cache Latency Google Lambda 79

HammerDB

OCTOBER 8, 2018

This post gives a HOWTO guide on system configuration for achieving top levels of performance with the HammerDB PostgreSQL TPC-C test. Firstly for system choice a 2 socket system is optimal for PostgreSQL OLTP performance at the time of writing. Make sure that your CPU is configured for optimal performance. Setting cpu: 0.

Best Practices 40

Best Practices Scalability Performance Hardware 40

HammerDB

OCTOBER 12, 2018

This post complements the previous best practice guides this time with the focus on MySQL and MariaDB and achieving top levels of performance with the HammerDB MySQL TPC-C test. As is exactly the same with PostgreSQL for system choice a 2 socket system is optimal for MySQL OLTP performance. hardware limits: 1000 MHz - 3.80

Best Practices 40

Best Practices Scalability Performance C++ 40