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 246

Engineering DevOps Government Latency 246

HammerDB

JULY 16, 2021

One of the most important concepts in analysing database performance is that of understanding scalability. When a system ‘scales’ it is able to deliver higher levels of performance proportional to the system resources available to it. In this example, we will compare MySQL 5.7.33 and MySQL 8.0.25 and MySQL 5.7.33.

Virtualization 57

Virtualization Performance C++ Database 57

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 167

Engineering DevOps Government Latency 167

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

All Things Distributed

DECEMBER 18, 2012

Werner Vogels weblog on building scalable and robust distributed systems. May 28 - Virtual Time and Global States of Distributed Systems , Friedemann Mattern, Parallel and Distributed Algorithms, North-Holland (1989) , p. July 20 Xen and the art of virtualization by Paul Barham, Boris Dragovic, Keir Fraser, Steven Hand, Timothy L.

Operating System 144

Operating System Cache AWS Scalability 144

HammerDB

JULY 5, 2022

This post addresses both questions to illustrate exactly why HammerDB is written in Tcl and why using Python to benchmark a database can result in poor performance and misleading results. As our results show the more threads we add the worse the performance gets due to this GIL synchronization. Surely any language will do? wait: 0.0

Benchmarking 98

Benchmarking Database C++ Virtualization 98

HammerDB

NOVEMBER 30, 2018

This article Threads Done Right… With Tcl gives an excellent overview of these capabilities and it should be clear that to build a scalable benchmarking tool this thread performance and scalability is key. Virtual Users. Virtual Users within HammerDB are operating system threads. HammerDB CLI v3.1

Architecture 40

Architecture Virtualization Open Source C++ 40