Dynatrace

FEBRUARY 4, 2021

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

Engineering 255

Engineering DevOps Government Latency 255

Dynatrace

FEBRUARY 4, 2021

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

Engineering 176

Engineering DevOps Government Latency 176

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. To think about it another way, site reliability engineering is where the traditional IT role, or system administration role, and DevOps meet. At that time, the team was made up of software engineers.

Engineering 67

Engineering DevOps Monitoring Google 67

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. HPCG is led by Japan’s RIKEN Fugaku system at 16 petaflops, which is 3% of it’s peak capacity. Next generation architectures will use CXL3.0

Architecture 52

Architecture Latency Benchmarking AWS 52

Smashing Magazine

AUGUST 20, 2021

Throughout the web’s history, static websites have always been a popular option due to their simplicity, scalability, and security. During the 90s, we saw two content management systems for static sites — Microsoft FrontPage in 1996 and Macromedia Dreamweaver in 1997. Aug 31 & Sep 1, 2021. Jump to the workshop ?.

Ecommerce 140

Ecommerce Website Government Internet 140

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. maximum transition latency: Cannot determine or is not supported.

Best Practices 40

Best Practices Scalability Performance Hardware 40

HammerDB

OCTOBER 12, 2018

As with the previous guides as an Intel employee (#IAMINTEL) the examples are taken from a MySQL 8 on Linux on Intel system and the approach is the same for whatever system you are testing although some of the settings you see may be different. System Setup: CPU, Memory and I/O Configuration. hardware limits: 1000 MHz - 3.80

Best Practices 40

Best Practices Scalability Performance C++ 40