Remove 2016 Remove Benchmarking Remove Speed Remove Storage
article thumbnail

SQL Server 2016 – It Just Runs Faster: Always On Availability Groups Turbocharged

SQL Server According to Bob

When we released Always On Availability Groups in SQL Server 2012 as a new and powerful way to achieve high availability, hardware environments included NUMA machines with low-end multi-core processors and SATA and SAN drives for storage (some SSDs). This chart shows our scaled results using a OLTP workload derived from TPC benchmarks.

article thumbnail

WAL Compression in PostgreSQL and Recent Improvements in Version 15

Percona

Some of the built-in features ( wal_compression ) have been there since 2016, and almost all backup tools do the WAL compression before taking it to the backup repository. Attempts to compress PostgreSQL WAL at different levels have always been around since the beginning. But this comes with a considerable performance implication.

Database 115
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

AMD EPYC Processors in Azure Virtual Machines

SQL Performance

Back on December 5, 2017, Microsoft announced that they were using AMD EPYC 7551 processors in their storage-optimized Lv2-Series virtual machines. This processor has a base clock speed of 2.0GHz, with an all-core boost speed of 2.55GHz, and a max boost clock speed of 3.0GHz. Figure 1: CPU-Z Benchmark Results for LS16v2.

Azure 42
article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

Back in 2016, I gave a talk outlining the causes and effects of the terrible performance of web apps built using popular tools on the fastest-growing device segment: low-end to mid-range Android phones. A then-representative $200USD device had 4-8 slow (in-order, low-cache) cores, ~2GiB of RAM, and relatively slow MLC NAND flash storage.

article thumbnail

Can You Afford It?: Real-world Web Performance Budgets

Alex Russell

Budgets are scaled to a benchmark network & device. JavaScript is the single most expensive part of any page in ways that are a function of both network capacity and device speed. Deciding what benchmark to use for a performance budget is crucial. The true median device from 2016 sold at about ~$200 unlocked.